mbox series

[0/4] ASoC: mediatek: remove cppcheck warnings

Message ID 20210311004904.121205-1-pierre-louis.bossart@linux.intel.com (mailing list archive)
Headers show
Series ASoC: mediatek: remove cppcheck warnings | expand

Message

Pierre-Louis Bossart March 11, 2021, 12:49 a.m. UTC
There should be no functionality change, this patchset only fixes
shadowed variables, prototypes and removes a useless assignment.

Pierre-Louis Bossart (4):
  ASoC: mediatek: mtk-btcvsd: remove useless assignment
  ASoC: mediatek: mt2701: align function prototype
  ASoC: mediatek: mt2701: rename shadowed array
  ASoC: mediatek: mt8173: rename local irq variable

 sound/soc/mediatek/common/mtk-btcvsd.c            | 2 +-
 sound/soc/mediatek/mt2701/mt2701-afe-clock-ctrl.h | 4 ++--
 sound/soc/mediatek/mt2701/mt2701-afe-pcm.c        | 4 ++--
 sound/soc/mediatek/mt8173/mt8173-afe-pcm.c        | 6 +++---
 4 files changed, 8 insertions(+), 8 deletions(-)

Comments

Mark Brown March 12, 2021, 8:23 p.m. UTC | #1
On Wed, 10 Mar 2021 18:49:00 -0600, Pierre-Louis Bossart wrote:
> There should be no functionality change, this patchset only fixes
> shadowed variables, prototypes and removes a useless assignment.
> 
> Pierre-Louis Bossart (4):
>   ASoC: mediatek: mtk-btcvsd: remove useless assignment
>   ASoC: mediatek: mt2701: align function prototype
>   ASoC: mediatek: mt2701: rename shadowed array
>   ASoC: mediatek: mt8173: rename local irq variable
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: mediatek: mtk-btcvsd: remove useless assignment
      commit: 2e5e57f085a3243aae7e4af88dc2c40e5ff4d3be
[2/4] ASoC: mediatek: mt2701: align function prototype
      commit: 57f1379e77a7432759e2f35b720c71863e2d83bc
[3/4] ASoC: mediatek: mt2701: rename shadowed array
      commit: d9cdc1335622866c52a463325b3aaea9844cff1b
[4/4] ASoC: mediatek: mt8173: rename local irq variable
      commit: 14667403a5631ce2fd2935d90c6d36f7975f61f3

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