linux-kernel - Re: [PATCH 0/2] ASoC: amd: ps: Propagate the PCI subsystem Vendor and Device IDs

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: <176107273005.196841.13422542346665726617.b4-ty@kernel.org>
Date: Tue, 21 Oct 2025 19:52:10 +0100
From: Mark Brown <broonie@...nel.org>
To: Simon Trimmer <simont@...nsource.cirrus.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 patches@...nsource.cirrus.com, Vijendar.Mukunda@....com
Subject: Re: [PATCH 0/2] ASoC: amd: ps: Propagate the PCI subsystem Vendor
 and Device IDs

On Thu, 16 Oct 2025 15:06:47 +0000, Simon Trimmer wrote:
> This chain of two patches propagates the PCI subsystem Vendor and Device
> IDs so that they can be used by component drivers to differentiate
> firmware loads.
> 
> Simon Trimmer (2):
>   ASoC: amd: ps: Propagate the PCI subsystem Vendor and Device IDs
>   ASoC: amd: amd_sdw: Propagate the PCI subsystem Vendor and Device IDs
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: amd: ps: Propagate the PCI subsystem Vendor and Device IDs
      commit: aab1301cfde344f966bbc442a4e655867ab56768
[2/2] ASoC: amd: amd_sdw: Propagate the PCI subsystem Vendor and Device IDs
      commit: 6658472a3e2de08197acfe099ba71ee0e2505ecf

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