From: Mark Brown <broonie@kernel.org>
To: "Bard Liao" <yung-chuan.liao@linux.intel.com>,
"Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>,
"Kai Vehmanen" <kai.vehmanen@linux.intel.com>,
"Stefan Binding" <sbinding@opensource.cirrus.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH v1 0/2] ASoC: Add Intel machine driver support for CS35L63
Date: Thu, 22 May 2025 09:45:29 +0100 [thread overview]
Message-ID: <174790352962.11863.8143259383908066219.b4-ty@kernel.org> (raw)
In-Reply-To: <20250516152107.210994-1-sbinding@opensource.cirrus.com>
On Fri, 16 May 2025 16:20:46 +0100, Stefan Binding wrote:
> This adds support to the Intel machine drivers for CS35L63 codecs using
> soundwire, and also adds match entries for the CDB35L63-CB2 on MTL
> systems.
>
> Richard Fitzgerald (1):
> ASoC: Intel: soc-acpi-intel-mtl-match: Add match for CDB35L63-CB2
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: intel: sof_sdw: Add support for CS35L63 into machine driver
commit: 898cd43bde30744e0b821efdf960781c240d4e6c
[2/2] ASoC: Intel: soc-acpi-intel-mtl-match: Add match for CDB35L63-CB2
commit: 8c4d2cc1e1cb9b8c9f26af6c5f19e0c7233e6f81
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
prev parent reply other threads:[~2025-05-22 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 15:20 [PATCH v1 0/2] ASoC: Add Intel machine driver support for CS35L63 Stefan Binding
2025-05-16 15:20 ` [PATCH v1 1/2] ASoC: intel: sof_sdw: Add support for CS35L63 into machine driver Stefan Binding
2025-05-16 15:20 ` [PATCH v1 2/2] ASoC: Intel: soc-acpi-intel-mtl-match: Add match for CDB35L63-CB2 Stefan Binding
2025-05-22 8:45 ` 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=174790352962.11863.8143259383908066219.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=sbinding@opensource.cirrus.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