linux-kernel - Re: [PATCH 1/5] ASoC: SDCA: Add missing header includes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <173508983900.596917.320979208067796021.b4-ty@kernel.org>
Date: Wed, 25 Dec 2024 01:23:59 +0000
From: Mark Brown <broonie@...nel.org>
To: Charles Keepax <ckeepax@...nsource.cirrus.com>
Cc: lgirdwood@...il.com, peter.ujfalusi@...ux.intel.com, 
 yung-chuan.liao@...ux.intel.com, pierre-louis.bossart@...ux.dev, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 patches@...nsource.cirrus.com
Subject: Re: [PATCH 1/5] ASoC: SDCA: Add missing header includes

On Fri, 20 Dec 2024 17:35:12 +0000, Charles Keepax wrote:
> Several of the SDCA files don't include all the headers they use
> locally. These are included by the point of use through other
> headers, so it is not currently causing any issues. However, files
> should directly include things they directly use, so add the
> missing header includes.
> 
> 
> [...]

Applied to

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

Thanks!

[1/5] ASoC: SDCA: Add missing header includes
      commit: deb015208f7be9a62cb68dd8337d075b1829ee1d
[2/5] ASoC: SDCA: Clean up error messages
      commit: 935cd06bfad4b715195befaf527a2d4fd36361d9
[3/5] ASoC: SDCA: Add bounds check for function address
      commit: c36297b1bd6e52a75a8ed75eb5dbf35c50402398
[4/5] ASoC: SDCA: Add missing function type names
      commit: c1ed5eb13f39b0058670bc2b1e251a040c306868
[5/5] ASoC: SDCA: Split function type patching and function naming
      commit: 69dcf023f1f13ca9c2e9e8f30b9ec52ac0486c0a

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