Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: lgirdwood@gmail.com, vkoul@kernel.org,
	yung-chuan.liao@linux.intel.com,  pierre-louis.bossart@linux.dev,
	peter.ujfalusi@linux.intel.com,  shumingf@realtek.com,
	linux-sound@vger.kernel.org,  patches@opensource.cirrus.com
Subject: Re: [PATCH 0/3] SDCA Jack Fixups
Date: Mon, 22 Dec 2025 20:58:45 +0000	[thread overview]
Message-ID: <176643712543.2127897.15726604656127454281.b4-ty@kernel.org> (raw)
In-Reply-To: <20251215153650.3913117-1-ckeepax@opensource.cirrus.com>

On Mon, 15 Dec 2025 15:36:46 +0000, Charles Keepax wrote:
> Some fixups to the jack handling, adding some necessary hooks to connect
> things with the machine driver. I have split these out from the system
> suspend chain as that has been generating a fair amount of discussion
> and getting these 3 merged is far more important to get basic
> functionality working smoothly. I will do a spin of the system suspend
> stuff soon, if either no new comments pop up, or we reach some consensus
> on how to proceed.
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: SDCA: Factor out jack handling into new c file
      commit: 3addd63d1fba8d9013e00b06d9420e39271c0c4e
[2/3] ASoC: SDCA: Add ability to connect SDCA jacks to ASoC jacks
      commit: 82e12800f563baf663277ef0017f40a335b8e84c
[3/3] ASoC: SDCA: Add ASoC jack hookup in class driver
      commit: 99a3ef1e81cd1775bc1f8cc2ad188b1fc755d5cd

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:[~2025-12-22 20:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15 15:36 [PATCH 0/3] SDCA Jack Fixups Charles Keepax
2025-12-15 15:36 ` [PATCH RESEND 1/3] ASoC: SDCA: Factor out jack handling into new c file Charles Keepax
2025-12-15 15:36 ` [PATCH RESEND 2/3] ASoC: SDCA: Add ability to connect SDCA jacks to ASoC jacks Charles Keepax
2025-12-15 15:36 ` [PATCH RESEND 3/3] ASoC: SDCA: Add ASoC jack hookup in class driver Charles Keepax
2025-12-19  1:58 ` [PATCH 0/3] SDCA Jack Fixups Liao, Bard
2025-12-22 20:58 ` 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=176643712543.2127897.15726604656127454281.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=shumingf@realtek.com \
    --cc=vkoul@kernel.org \
    --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