mbox series

[0/5] ASoC: remove more cppcheck warnings

Message ID 20210416191144.27006-1-pierre-louis.bossart@linux.intel.com
Headers show
Series ASoC: remove more cppcheck warnings | expand

Message

Pierre-Louis Bossart April 16, 2021, 7:11 p.m. UTC 
I missed those warnings in the previous rounds, they are mostly
trivial and shouldn't change the behavior.

Pierre-Louis Bossart (5):
  ASoC: soc-acpi: remove useless initialization
  ASoC: soc-core: fix signed/unsigned issue
  ASoC: soc-core: fix always-false condition
  ASoC: codecs: lpass-rx-macro: remove useless return
  ASoC: codecs: rt5682: clarify expression

 sound/soc/codecs/lpass-rx-macro.c | 2 --
 sound/soc/codecs/rt5682.c         | 2 +-
 sound/soc/soc-acpi.c              | 2 +-
 sound/soc/soc-core.c              | 7 +------
 4 files changed, 3 insertions(+), 10 deletions(-)

Comments

Mark Brown April 19, 2021, 5:33 p.m. UTC | #1 
On Fri, 16 Apr 2021 14:11:39 -0500, Pierre-Louis Bossart wrote:
> I missed those warnings in the previous rounds, they are mostly
> trivial and shouldn't change the behavior.
> 
> Pierre-Louis Bossart (5):
>   ASoC: soc-acpi: remove useless initialization
>   ASoC: soc-core: fix signed/unsigned issue
>   ASoC: soc-core: fix always-false condition
>   ASoC: codecs: lpass-rx-macro: remove useless return
>   ASoC: codecs: rt5682: clarify expression
> 
> [...]

Applied to

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

Thanks!

[1/5] ASoC: soc-acpi: remove useless initialization
      commit: 59ce3233a538fc21c5c59ff38cafd784cbcd6de0
[2/5] ASoC: soc-core: fix signed/unsigned issue
      commit: d3b47a888f0bc66a8590941cfa57ba015b288040
[3/5] ASoC: soc-core: fix always-false condition
      commit: e2290daefef3afa08135a0a65d4f0ce7fe23d5c0
[4/5] ASoC: codecs: lpass-rx-macro: remove useless return
      commit: 36924a12c32021a098fec621fb5ea707a72cd5b5
[5/5] ASoC: codecs: rt5682: clarify expression
      commit: 9726db36ed83670be93d053e05e150308e3ce743

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