mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
Cc: alsa-devel@alsa-project.org,
	pierre-louis.bossart@linux.intel.com,
	 yung-chuan.liao@linux.intel.com,
	ranjani.sridharan@linux.intel.com,  lgirdwood@gmail.com,
	perex@perex.cz, tiwai@suse.com,  Basavaraj.Hiregoudar@amd.com,
	Sunil-kumar.Dommati@amd.com,  venkataprasad.potturu@amd.com,
	kai.vehmanen@linux.intel.com,  ckeepax@opensource.cirrus.com,
	linux-sound@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] AMD SoundWire machine driver code refactor
Date: Fri, 13 Sep 2024 17:54:46 +0100	[thread overview]
Message-ID: <172624648667.60960.3648714524641692495.b4-ty@kernel.org> (raw)
In-Reply-To: <20240913090631.1834543-1-Vijendar.Mukunda@amd.com>

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@linux.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


      parent reply	other threads:[~2024-09-13 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13  9:06 Vijendar Mukunda
2024-09-13  9:06 ` [PATCH 1/5] ASoC: intel: sof_sdw: rename soundwire endpoint and dailink structures Vijendar Mukunda
2024-09-13  9:06 ` [PATCH 2/5] ASoC: intel: sof_sdw: rename soundwire parsing helper functions Vijendar Mukunda
2024-09-13  9:06 ` [PATCH 3/5] ASoC: sdw_util/intel: move soundwire endpoint and dai link structures Vijendar Mukunda
2024-09-13  9:06 ` [PATCH 4/5] ASoC: sdw_utils/intel: move soundwire endpoint parsing helper functions Vijendar Mukunda
2024-09-13  9:06 ` [PATCH 5/5] ASoC: amd: acp: refactor SoundWire machine driver code Vijendar Mukunda
2024-09-13 16:54 ` Mark Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=172624648667.60960.3648714524641692495.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=Basavaraj.Hiregoudar@amd.com \
    --cc=Sunil-kumar.Dommati@amd.com \
    --cc=Vijendar.Mukunda@amd.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=tiwai@suse.com \
    --cc=venkataprasad.potturu@amd.com \
    --cc=yung-chuan.liao@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®