[0/6] ASoC: rt5682: apply some refactors

Message

Tzung-Bi Shih April 30, 2020, 8:22 a.m. UTC

The series tries to refactor the coding style to follow most conventions.

The 4th patch converts pr_() to dev_().
(https://mailman.alsa-project.org/pipermail/alsa-devel/2020-March/164849.html)

The 6th patch changes the behavior a bit to restore its original intent.

Tzung-Bi Shih (6):
  ASoC: rt5682: simplify assertions
  ASoC: rt5682: fix space issues
  ASoC: rt5682: remove empty default case
  ASoC: rt5682: replace message printing from pr_() to dev_()
  ASoC: rt5682: remove duplicate rt5682_reset() calls
  ASoC: rt5682: remove unwanted btn_type assignment

 sound/soc/codecs/rt5682.c | 198 ++++++++++++++++----------------------
 1 file changed, 84 insertions(+), 114 deletions(-)

Comments

Mark Brown April 30, 2020, 1:40 p.m. UTC | #1

On Thu, 30 Apr 2020 16:22:25 +0800, Tzung-Bi Shih wrote:
> The series tries to refactor the coding style to follow most conventions.
> 
> The 4th patch converts pr_() to dev_().
> (https://mailman.alsa-project.org/pipermail/alsa-devel/2020-March/164849.html)
> 
> The 6th patch changes the behavior a bit to restore its original intent.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.8

Thanks!

[1/6] ASoC: rt5682: simplify assertions
      commit: 38c2e325a66b1c4d694d2a15b5efa81e5ae38872
[2/6] ASoC: rt5682: fix space issues
      commit: 5b8e09091b6092296a209a940e192ed2cc891efe
[3/6] ASoC: rt5682: remove empty default case
      commit: 70255cf6917828a2caf93f79f15a09bd71803e61
[4/6] ASoC: rt5682: replace message printing from pr_() to dev_()
      commit: 9c1cb755b5b325c18551f7d08438ea6896130acd
[5/6] ASoC: rt5682: remove duplicate rt5682_reset() calls
      commit: 2317e84979fb80821c0d3ef909f1a2b68ace37f9
[6/6] ASoC: rt5682: remove unwanted btn_type assignment
      commit: 4642126b852f46d5d6a16bc60d50fbe4920c2710

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark