Message ID | 20200702164433.162815-1-pierre-louis.bossart@linux.intel.com (mailing list archive) |
---|---|
Headers | show |
Series | ASoC: amd: remove warnings with make W=1 | expand |
On Thu, 2 Jul 2020 11:44:27 -0500, Pierre-Louis Bossart wrote: > Yet another cleanup series, with good findings of variables not used > for anything. > > Pierre-Louis Bossart (6): > ASoC: amd: acp-da7219-max98357a: fix 'defined but not used' warning > ASoC: amd: acp-rt5645: fix 'defined but not used' warning > ASoC: amd: raven: acp3x-pcm-dma: fix 'set but not used' warning > ASoC: amd: raven: acp3x-i2s: fix 'set but not used' warning > ASoC: amd: raven: acp3x-pcm-dma: remove unused-but-set variable > ASoC: amd: raven: acp3x-i2s: remove unused-but-set variable > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/6] ASoC: amd: acp-da7219-max98357a: fix 'defined but not used' warning commit: dc1aff7f0d1b79e17026e08b14d7bb60ccdae1c8 [2/6] ASoC: amd: acp-rt5645: fix 'defined but not used' warning commit: 41e4a5b32af6ccec4e11a1cbd20c5569d20faa24 [3/6] ASoC: amd: raven: acp3x-pcm-dma: fix 'set but not used' warning commit: 5ec2978f1e7494065d1b44e20b047e5840fd7ca7 [4/6] ASoC: amd: raven: acp3x-i2s: fix 'set but not used' warning commit: fadecf947a72f54843afa12c6732c52914d5024d [5/6] ASoC: amd: raven: acp3x-pcm-dma: remove unused-but-set variable commit: 16607237f3b6a56ace8cdbd19bb793cb9bb3f18e [6/6] ASoC: amd: raven: acp3x-i2s: remove unused-but-set variable commit: 343403e2dad897a3c6c974a43d760b4fb96b996b 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