From: Mark Brown <broonie@kernel.org>
To: Vitaly Rodionov <vitalyr@opensource.cirrus.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
David Rhodes <david.rhodes@cirrus.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com, devicetree@vger.kernel.org
Subject: Re: (subset) [PATCH v4 00/11] Add support for Cirrus Logic CS530x DAC and CODEC variants.
Date: Tue, 21 Oct 2025 13:11:34 +0100 [thread overview]
Message-ID: <176104869443.31596.194072100832387720.b4-ty@kernel.org> (raw)
In-Reply-To: <20251017161543.214235-1-vitalyr@opensource.cirrus.com>
On Fri, 17 Oct 2025 17:15:27 +0100, Vitaly Rodionov wrote:
> This patch series introduces DAC, CODEC, and SPI control bus support
> for Cirrus Logic CS530x variants, along with general code cleanup
> and resolution of checkpatch.pl warnings.
>
> Changes since v1,v2,v3:
>
> - Signed off all patches
> - Splitted "tidy up" pach in 3 separate simple patches
> - Fixed commit subject to much preferred subject prefix for binding patches.
> - Moved dt-bindings related patch down the chain
> - Added all relevant maintainers to CC list
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[01/11] ASoC: cs530x: Correct log message with expected variable
commit: 248adfe32bfd75afbcb8f6d4b68f7e0a9fb2c438
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-10-21 12:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 16:15 [PATCH v4 00/11] Add support for Cirrus Logic CS530x DAC and CODEC variants Vitaly Rodionov
2025-10-17 16:15 ` [PATCH v4 01/11] ASoC: cs530x: Correct log message with expected variable Vitaly Rodionov
2025-10-17 16:15 ` [PATCH v4 02/11] ASoC: cs530x: Update the copyright headers Vitaly Rodionov
2025-10-17 16:15 ` [PATCH v4 03/11] ASoC: cs530x: Sort #include directives and tidy up whitespaces Vitaly Rodionov
2025-10-17 16:15 ` [PATCH v4 04/11] ASoC: cs530x: Remove unused struct members and constants Vitaly Rodionov
2025-10-17 16:28 ` Mark Brown
2025-10-17 16:15 ` [PATCH v4 05/11] ASoC: cs530x: Correct constant naming Vitaly Rodionov
2025-10-17 16:15 ` [PATCH v4 06/11] ASoC: dt-bindings: sound: cirrus: cs530x: Add cs530x variants Vitaly Rodionov
2025-10-17 16:31 ` Mark Brown
2025-10-17 16:46 ` Vitaly Rodionov
2025-10-19 10:32 ` Krzysztof Kozlowski
2025-10-19 14:23 ` Vitaly Rodionov
2025-10-17 16:15 ` [PATCH v4 07/11] ASoC: cs530x: Add CODEC and DAC support Vitaly Rodionov
2025-10-17 16:41 ` Mark Brown
2025-10-17 16:15 ` [PATCH v4 08/11] ASoC: cs530x: Check the DEVID matches the devtype Vitaly Rodionov
2025-10-17 16:15 ` [PATCH v4 09/11] ASoC: cs530x: Correct MCLK reference frequency values Vitaly Rodionov
2025-10-17 16:44 ` Mark Brown
2025-10-17 16:57 ` Vitaly Rodionov
2025-10-17 16:15 ` [PATCH v4 10/11] ASoC: cs530x: Rename i2c related structures Vitaly Rodionov
2025-10-17 16:15 ` [PATCH v4 11/11] ASoC: cs530x: Add SPI bus support for cs530x parts Vitaly Rodionov
2025-10-17 16:46 ` Mark Brown
2025-10-21 12:11 ` 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=176104869443.31596.194072100832387720.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david.rhodes@cirrus.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=rf@opensource.cirrus.com \
--cc=robh@kernel.org \
--cc=tiwai@suse.com \
--cc=vitalyr@opensource.cirrus.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