From: Krzysztof Kozlowski <krzk@kernel.org>
To: Vitaly Rodionov <vitalyr@opensource.cirrus.com>,
Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH 8/8] ASoC: cs530x: Add DT compartible strings
Date: Thu, 16 Oct 2025 07:42:42 +0200 [thread overview]
Message-ID: <b90e6b37-478e-42dd-9afd-4c6a44580228@kernel.org> (raw)
In-Reply-To: <20251015092619.52952-9-vitalyr@opensource.cirrus.com>
On 15/10/2025 11:26, Vitaly Rodionov wrote:
> Signed-off-by: Vitaly Rodionov <vitalyr@opensource.cirrus.com>
> ---
> Documentation/devicetree/bindings/sound/cirrus,cs530x.yaml | 4 ++++
1.
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.
You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time.
Please kindly resend and include all necessary To/Cc entries.
2. Also, missing commit msg.
3. Please use subject prefixes matching the subsystem. You can get them
for example with `git log --oneline -- DIRECTORY_OR_FILE` on the
directory your patch is touching. For bindings, the preferred subjects
are explained here:
https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters
4. Please organize the patch documenting compatible (DT bindings) before
their user.
See also:
https://elixir.bootlin.com/linux/v6.14-rc6/source/Documentation/devicetree/bindings/submitting-patches.rst#L46
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/sound/cirrus,cs530x.yaml b/Documentation/devicetree/bindings/sound/cirrus,cs530x.yaml
> index 9582eb8eb418..90a5cea0632d 100644
> --- a/Documentation/devicetree/bindings/sound/cirrus,cs530x.yaml
> +++ b/Documentation/devicetree/bindings/sound/cirrus,cs530x.yaml
> @@ -22,6 +22,10 @@ properties:
> - cirrus,cs5302
> - cirrus,cs5304
> - cirrus,cs5308
> + - cirrus,cs4282
> + - cirrus,cs4302
> + - cirrus,cs4304
> + - cirrus,cs4308
Keep the order.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-10-16 5:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 9:26 [PATCH 0/8] Add support for Cirrus Logic CS530x DAC and CODEC variants Vitaly Rodionov
2025-10-15 9:26 ` [PATCH 1/8] ASoC: cs530x: Correct log message with expected variable Vitaly Rodionov
2025-10-15 10:13 ` Mark Brown
2025-10-15 9:26 ` [PATCH 2/8] ASoC: cs530x: Tidy up driver before adding more features Vitaly Rodionov
2025-10-15 10:11 ` Mark Brown
2025-10-15 9:26 ` [PATCH 3/8] ASoC: cs530x: Add CODEC and DAC support Vitaly Rodionov
2025-10-15 9:26 ` [PATCH 4/8] ASoC: cs530x: Check the DEVID matches the devtype Vitaly Rodionov
2025-10-15 9:26 ` [PATCH 5/8] ASoC: cs530x: Correct MCLK reference frequency values Vitaly Rodionov
2025-10-15 9:26 ` [PATCH 6/8] ASoC: cs530x: Rename i2c related structures Vitaly Rodionov
2025-10-15 9:26 ` [PATCH 7/8] ASoC: cs530x: Add SPI bus support for cs530x parts Vitaly Rodionov
2025-10-15 9:26 ` [PATCH 8/8] ASoC: cs530x: Add DT compartible strings Vitaly Rodionov
2025-10-16 5:42 ` Krzysztof Kozlowski [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=b90e6b37-478e-42dd-9afd-4c6a44580228@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@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=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