[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <170847652092.70487.7212581816199412994.b4-ty@kernel.org>
Date: Wed, 21 Feb 2024 00:48:40 +0000
From: Mark Brown <broonie@...nel.org>
To: Vijendar Mukunda <Vijendar.Mukunda@....com>
Cc: alsa-devel@...a-project.org, Basavaraj.Hiregoudar@....com,
Sunil-kumar.Dommati@....com, Mario.Limonciello@....com,
venkataprasad.potturu@....com, Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
Arnd Bergmann <arnd@...db.de>,
Cristian Ciocaltea <cristian.ciocaltea@...labora.com>,
Lucas Tanure <lucas.tanure@...labora.com>,
Syed Saba Kareem <Syed.SabaKareem@....com>,
Carlos Bilbao <carlos.bilbao@....com>,
Mario Limonciello <mario.limonciello@....com>,
"open list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM..." <linux-sound@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/5] ASoC: amd: ps: refactor acp device configuration
read logic
On Wed, 14 Feb 2024 16:10:01 +0530, Vijendar Mukunda wrote:
> Refactor acp device configuration read logic and use common function
> to scan SoundWire devices.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/5] ASoC: amd: ps: refactor acp device configuration read logic
commit: 0386d765f27a1fd3ed2ed6388a07e26d9659936d
[2/5] ASoC: amd: ps: refactor acp child platform device creation code
commit: eaf825037d6df89811d43391be920bf6ad731463
[3/5] ASoC: amd: ps: remove acp_reset flag
commit: 3c697ced399cac295c34c9611f05d04f4c951aa9
[4/5] ASoC: amd: ps: fix for acp pme wake for soundwire configuration
commit: c76f3b1f9b9ae20f8c944bb01c395329d525a917
[5/5] ASoC: amd: ps: add machine select and register code
commit: bbf3e6145ea09cf346ce09146b0b98415095f170
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