linux-kernel - Re: (subset) [PATCH 0/7] Adjust all AMD audio drivers to use AMD

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: <174000648081.2064138.16099679978882177609.b4-ty@kernel.org>
Date: Wed, 19 Feb 2025 23:08:00 +0000
From: Mark Brown <broonie@...nel.org>
To: Yazen Ghannam <yazen.ghannam@....com>, Borislav Petkov <bp@...en8.de>, 
 Mario Limonciello <superm1@...nel.org>
Cc: Mario Limonciello <mario.limonciello@....com>, 
 Thomas Gleixner <tglx@...utronix.de>, 
 Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org, 
 "H . Peter Anvin" <hpa@...or.com>, Liam Girdwood <lgirdwood@...il.com>, 
 Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>, 
 Peter Ujfalusi <peter.ujfalusi@...ux.intel.com>, 
 Bard Liao <yung-chuan.liao@...ux.intel.com>, 
 Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>, 
 Daniel Baluta <daniel.baluta@....com>, 
 Kai Vehmanen <kai.vehmanen@...ux.intel.com>, 
 Pierre-Louis Bossart <pierre-louis.bossart@...ux.dev>, 
 Vijendar Mukunda <Vijendar.Mukunda@....com>, 
 Peter Zijlstra <peterz@...radead.org>, 
 Jeff Johnson <quic_jjohnson@...cinc.com>, 
 Venkata Prasad Potturu <venkataprasad.potturu@....com>, 
 Uwe Kleine-König <u.kleine-koenig@...libre.com>, 
 Arnd Bergmann <arnd@...db.de>, 
 Cristian Ciocaltea <cristian.ciocaltea@...labora.com>, 
 Krzysztof Kozlowski <krzk@...nel.org>, linux-kernel@...r.kernel.org, 
 linux-sound@...r.kernel.org, sound-open-firmware@...a-project.org
Subject: Re: (subset) [PATCH 0/7] Adjust all AMD audio drivers to use
 AMD_NODE

On Mon, 17 Feb 2025 17:17:40 -0600, Mario Limonciello wrote:
> The various AMD audio drivers have self contained implementations
> for SMN router communication that require hardcoding the bridge ID.
> 
> These implementations also don't prevent race conditions with other
> drivers performing SMN communication.
> 
> A new centralized driver AMD_NODE is introduced and all drivers in
> the kernel should use this instead. Adjust all AMD audio drivers to
> use it.
> Mario Limonciello (7):
>   x86/amd_node: Add a helper for use with `read_poll_timeout`
>   ASoC: amd: acp: rembrandt: Use AMD_NODE
>   ASoC: amd: acp: acp70: Use AMD_NODE
>   ASoC: amd: acp: acp63: Use AMD_NODE
>   ASoC: SOF: amd: Use AMD_NODE
>   ASoC: amd: acp: Drop local symbols for smn read/write
>   ASoC: SOF: amd: Drop host bridge ID from struct
> 
> [...]

Applied to

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

Thanks!

[2/7] ASoC: amd: acp: rembrandt: Use AMD_NODE
      commit: e211adcf36d0ccdd31af7398af4725a47d74b3d4
[3/7] ASoC: amd: acp: acp70: Use AMD_NODE
      commit: 135c6af1cac5465529469700d16c0c44b24ce317
[4/7] ASoC: amd: acp: acp63: Use AMD_NODE
      commit: 8f969537149d672d40a0e75a83f39451a5402780
[5/7] ASoC: SOF: amd: Use AMD_NODE
      commit: f120cf33d2325fd95d063eccbff2e86ffc7f493a
[6/7] ASoC: amd: acp: Drop local symbols for smn read/write
      commit: 40d05927830227f2a1701c61e8bbe65287a03490
[7/7] ASoC: SOF: amd: Drop host bridge ID from struct
      commit: a261d77fec147b9974aacca8ae8f0693feede838

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