linux-kernel - Re: [PATCH 0/2] Add SoundWire machines for ACP7.0/ACP7.1 sof stack

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: <175087319206.198995.12597800532047615959.b4-ty@kernel.org>
Date: Wed, 25 Jun 2025 18:39:52 +0100
From: Mark Brown <broonie@...nel.org>
To: Vijendar Mukunda <Vijendar.Mukunda@....com>
Cc: alsa-devel@...a-project.org, lgirdwood@...il.com, 
 yung-chuan.liao@...ux.intel.com, pierre-louis.bossart@...ux.dev, 
 perex@...ex.cz, tiwai@...e.com, Basavaraj.Hiregoudar@....com, 
 Sunil-kumar.Dommati@....com, venkataprasad.potturu@....com, 
 mario.limonciello@....com, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, sound-open-firmware@...a-project.org
Subject: Re: [PATCH 0/2] Add SoundWire machines for ACP7.0/ACP7.1 sof stack

On Fri, 20 Jun 2025 17:38:41 +0530, Vijendar Mukunda wrote:
> Add SoundWire machines as alternate machines for ACP7.0 & ACP7.1
> platforms with the below machine configuration.
> Link 0: RT722 codec with three endpoints: Headset, Speaker, and DMIC.
> 
> Vijendar Mukunda (2):
>   ASoC: amd: acp: add soundwire machine for ACP7.0 and ACP7.1 sof stack
>   ASoC: SOF: amd: add alternate machines for ACP7.0 and ACP7.1 platforms
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: amd: acp: add soundwire machine for ACP7.0 and ACP7.1 sof stack
      commit: 8b04b766714e93ca5a8021ff3408c9ef89d9eb85
[2/2] ASoC: SOF: amd: add alternate machines for ACP7.0 and ACP7.1 platforms
      commit: 59566923d955b69bfb1e1163f07dff437dde8c9c

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