[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174659471540.4169088.2896331168566981958.b4-ty@kernel.org>
Date: Wed, 07 May 2025 14:11:55 +0900
From: Mark Brown <broonie@...nel.org>
To: Vijendar Mukunda <Vijendar.Mukunda@....com>
Cc: alsa-devel@...a-project.org, lgirdwood@...il.com, perex@...ex.cz,
tiwai@...e.com, yung-chuan.liao@...ux.intel.com,
ranjani.sridharan@...ux.intel.com, pierre-louis.bossart@...ux.dev,
Basavaraj.Hiregoudar@....com, Sunil-kumar.Dommati@....com,
venkataprasad.potturu@....com, Mario.Limonciello@....com,
linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH 1/3] ASoC: amd: amd_sdw: Fix unlikely uninitialized
variable use in create_sdw_dailinks()
On Tue, 06 May 2025 17:37:22 +0530, Vijendar Mukunda wrote:
> Initialize current_be_id to 0 in AMD legacy stack(NO DSP enabled) SoundWire
> generic machine driver code to handle the unlikely case when there are no
> devices connected to a DAI.
>
> In this case create_sdw_dailink() would return without touching the passed
> pointer to current_be_id.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] ASoC: amd: amd_sdw: Fix unlikely uninitialized variable use in create_sdw_dailinks()
commit: 4d87ae7508cb7ff58fd0bcecc6e9491f42f987f8
[2/3] ASoC: amd: sof_amd_sdw: Fix unlikely uninitialized variable use in create_sdw_dailinks()
commit: 6b83ba4bc3ecb915476d688c9f00f3be57b49a0c
[3/3] ASoC: amd: sof_amd_sdw: add logic to get cpu_pin_id for ACP7.0/ACP7.1 platforms
commit: ad6d689e776478113aeef7bfb0e4222b1ff2a986
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
Powered by blists - more mailing lists