[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <172624648667.60960.3648714524641692495.b4-ty@kernel.org>
Date: Fri, 13 Sep 2024 17:54:46 +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, kai.vehmanen@...ux.intel.com,
ckeepax@...nsource.cirrus.com, linux-sound@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] AMD SoundWire machine driver code refactor
On Fri, 13 Sep 2024 14:36:26 +0530, Vijendar Mukunda wrote:
> This patch series moves common Soundwire endpoint parsing and dai
> creation logic to common placeholder from Intel generic SoundWire
> machine driver code to make it generic. AMD SoundWire machine driver
> code is refactored to use these functions for SoundWire endpoint
> parsing and dai creation logic.
>
> Link: https://github.com/thesofproject/linux/pull/5171
> Reviewed-by: Bard Liao <yung-chuan.liao@...ux.intel.com>
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/5] ASoC: intel: sof_sdw: rename soundwire endpoint and dailink structures
commit: f5c05fd7e9d20a3a8f3401b467fec2d24f49ea5a
[2/5] ASoC: intel: sof_sdw: rename soundwire parsing helper functions
commit: 23f020bd607b7aec5f301699227ed196430fbc40
[3/5] ASoC: sdw_util/intel: move soundwire endpoint and dai link structures
commit: 7860df5b29945cfab40dd667f576af31401d7c43
[4/5] ASoC: sdw_utils/intel: move soundwire endpoint parsing helper functions
commit: 13b24f84782d6c0373f62eb645353883d94d1dcd
[5/5] ASoC: amd: acp: refactor SoundWire machine driver code
commit: 6d8348ddc56ed43ba39d1e8adda13299201f32ed
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