linux-kernel - Re: [PATCH 0/2] Add SOF support for ACP7.0 based platform

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: <172449440702.846858.10370645706025243690.b4-ty@kernel.org>
Date: Sat, 24 Aug 2024 11:13:27 +0100
From: Mark Brown <broonie@...nel.org>
To: Vijendar Mukunda <Vijendar.Mukunda@....com>
Cc: alsa-devel@...a-project.org, pierre-louis.bossart@...ux.intel.com, 
 yung-chuan.liao@...ux.intel.com, ranjani.sridharan@...ux.intel.com, 
 lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 Basavaraj.Hiregoudar@....com, Sunil-kumar.Dommati@....com, 
 venkataprasad.potturu@....com, cristian.ciocaltea@...labora.com, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] Add SOF support for ACP7.0 based platform

On Fri, 23 Aug 2024 11:07:37 +0530, Vijendar Mukunda wrote:
> This patch series adds SOF support for ACP7.0 based platform.
> 
> Link: https://github.com/thesofproject/linux/pull/5139
> 
> Vijendar Mukunda (2):
>   ASoC: amd: Add acpi machine id for acp7.0 version based platform
>   ASoC: SOF: amd: add support for acp7.0 based platform
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: amd: Add acpi machine id for acp7.0 version based platform
      commit: e17de785850e3112b2ea6ba786016a61f195bb23
[2/2] ASoC: SOF: amd: add support for acp7.0 based platform
      commit: 490be7ba2a018093fbfa6c2dd80d7d0c190c4c98

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