From: Mark Brown <broonie@kernel.org>
To: "Liam Girdwood" <lgirdwood@gmail.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
"Jonas Schwöbel" <jonasschwoebel@yahoo.de>,
"Svyatoslav Ryhel" <clamor95@gmail.com>
Cc: linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] ASoC: tegra: Add support for WM8962 and CPCAP codecs
Date: Tue, 03 Mar 2026 11:20:03 +0000 [thread overview]
Message-ID: <177253680370.22767.5594712156788646964.b4-ty@kernel.org> (raw)
In-Reply-To: <20260223065051.13070-1-clamor95@gmail.com>
On Mon, 23 Feb 2026 08:50:46 +0200, Svyatoslav Ryhel wrote:
> Add support for WM8962 and CPCAP codecs found in various Tegra devices.
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/5] ASoC: dt-bindings: nvidia,tegra-audio: document CPCAP CODEC
commit: d6b634cbc2eed73497877c95a7807d0f34fa4459
[2/5] ASoC: tegra: Support CPCAP by machine driver
commit: a34547b389a91bf0709f0901c3752ccaf63730cd
[3/5] ASoC: dt-bindings: nvidia,tegra-audio: document WM8962 CODEC
commit: 79d73f5a0b7a702a19189c1a237ae3728d88de59
[4/5] ASoC: tegra: Support WM8962 by machine driver
commit: 536ffa105e16ca3f6e7de53f9d6059f53d0207f7
[5/5] ASoC: dt-bindings: nvidia,tegra-audio-max9808x: document additional board pins
commit: 06dba254de95b16e7793224d29daa5195de2e581
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:[~2026-03-03 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 6:50 Svyatoslav Ryhel
2026-02-23 6:50 ` [PATCH v3 1/5] ASoC: dt-bindings: nvidia,tegra-audio: document CPCAP CODEC Svyatoslav Ryhel
2026-02-23 6:50 ` [PATCH v3 2/5] ASoC: tegra: Support CPCAP by machine driver Svyatoslav Ryhel
2026-02-23 6:50 ` [PATCH v3 3/5] ASoC: dt-bindings: nvidia,tegra-audio: document WM8962 CODEC Svyatoslav Ryhel
2026-02-23 6:50 ` [PATCH v3 4/5] ASoC: tegra: Support WM8962 by machine driver Svyatoslav Ryhel
2026-02-23 6:50 ` [PATCH v3 5/5] ASoC: dt-bindings: nvidia,tegra-audio-max9808x: document additional board pins Svyatoslav Ryhel
2026-03-03 11:20 ` 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=177253680370.22767.5594712156788646964.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonasschwoebel@yahoo.de \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.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
all inboxes | Powered by JetHome®