Re: [PATCH 0/8] ASoC: minor cleanup of warnings

From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	alsa-devel@alsa-project.org
Cc: tiwai@suse.de
Subject: Re: [PATCH 0/8] ASoC: minor cleanup of warnings
Date: Wed, 27 Oct 2021 18:29:11 +0100	[thread overview]
Message-ID: <163535575198.4012075.17769018172349090714.b4-ty@kernel.org> (raw)
In-Reply-To: <20211025185933.144327-1-pierre-louis.bossart@linux.intel.com>

On Mon, 25 Oct 2021 13:59:25 -0500, Pierre-Louis Bossart wrote:
> Sparse, make W=1 and cppcheck all report minor warnings.
> 
> The only functional change is in patch7 where the error code is now
> returned to the caller.
> 
> Pierre-Louis Bossart (8):
>   ASoC: topology: handle endianness warning
>   ASoC: rt5682s: use 'static' qualifier
>   ASoC: nau8821: fix kernel-doc
>   ASoC: nau8821: clarify out-of-bounds check
>   ASoC: mediatek: remove unnecessary initialization
>   ASoC: mediatek: mt8195: rename shadowed array
>   ASoC: mediatek: mt8195: fix return value
>   ASoC: rockchip: i2s_tdm: improve return value handling
> 
> [...]

Applied to

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

Thanks!

[1/8] ASoC: topology: handle endianness warning
      commit: 1baad7dad115ea3976fb5e5d0e3f3bec83dfd7ca
[2/8] ASoC: rt5682s: use 'static' qualifier
      commit: 49ba5e936e1512d4c7812d433048f8909234fca0
[3/8] ASoC: nau8821: fix kernel-doc
      commit: 765e08bdc7faa44b13bf96df4663a580d68a1c49
[4/8] ASoC: nau8821: clarify out-of-bounds check
      commit: 46ae0b3f554a323322a770c0edee50aa8019a655
[5/8] ASoC: mediatek: remove unnecessary initialization
      commit: 33fb790fcc02a717c1cac90958f203f06da14f7e
[6/8] ASoC: mediatek: mt8195: rename shadowed array
      commit: 73983ad922764e747d40b486ec7c2526e0355db1
[7/8] ASoC: mediatek: mt8195: fix return value
      commit: 439c06f341aa1f09ad7def774998db1076946c98
[8/8] ASoC: rockchip: i2s_tdm: improve return value handling
      commit: f913582190ddfe2380ecf8ee87b4ff2c8dcb5d48

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