Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Mark Brown <broonie@kernel.org>,
	Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>,
	linux-sound@vger.kernel.org
Cc: lkp@intel.com, LKML <linux-kernel@vger.kernel.org>,
	Jaroslav Kysela <perex@perex.cz>,
	Dmitry Baryshkov <lumag@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Shenghao Ding <shenghao-ding@ti.com>,
	Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH] ASoC: codecs: wcd934x: add explicit soundwire depenency
Date: Sat, 22 Nov 2025 20:03:41 +0100	[thread overview]
Message-ID: <7392a065-bfc5-4dfa-89ac-a7ac94a587d9@web.de> (raw)
In-Reply-To: <176376310618.101329.9975086867710479356.b4-ty@kernel.org>

> Applied to
> 
>    https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
> 
> Thanks!
> 
> [1/1] ASoC: codecs: wcd934x: add explicit soundwire depenency
>       commit: a3d8f733d453ed4d4eb1f0e894eec787777465a2
> 
> 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.

Would any contributors care more to avoid a typo in the summary phrase?

Regards,
Markus

      reply	other threads:[~2025-11-22 19:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21 14:32 [PATCH] ASoC: codecs: wcd934x: add explicit soundwire depenency Srinivas Kandagatla
2025-11-21 22:11 ` Mark Brown
2025-11-22 19:03   ` Markus Elfring [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=7392a065-bfc5-4dfa-89ac-a7ac94a587d9@web.de \
    --to=markus.elfring@web.de \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lumag@kernel.org \
    --cc=perex@perex.cz \
    --cc=shenghao-ding@ti.com \
    --cc=srinivas.kandagatla@oss.qualcomm.com \
    --cc=tiwai@suse.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