linux-kernel - Re: [PATCH] ASoC: amd: acp: Return in-case of error

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <172562795750.927452.5890611265241212761.b4-ty@kernel.org>
Date: Fri, 06 Sep 2024 14:05:57 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, 
 Venkata Prasad Potturu <venkataprasad.potturu@....com>, 
 Syed Saba Kareem <Syed.SabaKareem@....com>, 
 Vijendar Mukunda <Vijendar.Mukunda@....com>, 
 Muhammad Usama Anjum <usama.anjum@...labora.com>
Cc: kernel@...labora.com, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: amd: acp: Return in-case of error

On Fri, 06 Sep 2024 15:37:24 +0500, Muhammad Usama Anjum wrote:
> Return when error occurs instead of proceeding to for loop which will
> use val uninitialized.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: amd: acp: Return in-case of error
      commit: 3c5a18a10a8c6fab27739e6e7bd0e4c0aa854d92

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