public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Vitaly Rodionov <vitalyr@opensource.cirrus.com>,
	Mark Brown <broonie@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: 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: [PATCH v6 05/12] ASoC: dt-bindings: sound: cirrus: cs530x: Add cs530x
Date: Thu, 23 Oct 2025 20:15:24 +0200	[thread overview]
Message-ID: <fa397247-6271-47eb-bea6-ccd83808df74@kernel.org> (raw)
In-Reply-To: <20251023090327.58275-6-vitalyr@opensource.cirrus.com>

On 23/10/2025 11:03, Vitaly Rodionov wrote:
> This patch adds additional cs530x family variants.
> 
> cirrus,cs4282 - high-performance, 32-bit resolution, stereo CODEC
> cirrus,cs4302 - high performance stereo DAC, 2 channels
> cirrus,cs4304 - high performance stereo DAC, 4 channels
> cirrus,cs4308 - high performance stereo DAC, 8 channels
> 

<form letter>
This is a friendly reminder during the review process.

It looks like you received a tag and forgot to add it.

If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions
of patchset, under or above your Signed-off-by tag, unless patch changed
significantly (e.g. new properties added to the DT bindings). Tag is
"received", when provided in a message replied to you on the mailing
list. Tools like b4 can help here. However, there's no need to repost
patches *only* to add the tags. The upstream maintainer will do that for
tags received on the version they apply.

Please read:
https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577

If a tag was not added on purpose, please state why and what changed.
</form letter>

Best regards,
Krzysztof

  parent reply	other threads:[~2025-10-23 18:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-23  9:03 [PATCH v6 00/12] Add support for Cirrus Logic CS530x DAC and CODEC variants Vitaly Rodionov
2025-10-23  9:03 ` [PATCH v6 01/12] ASoC: cs530x: Update the copyright headers Vitaly Rodionov
2025-10-23  9:03 ` [PATCH v6 02/12] ASoC: cs530x: Sort #include directives and tydy up whitespaces Vitaly Rodionov
2025-10-23  9:03 ` [PATCH v6 03/12] ASoC: cs530x: Remove unused struct members and constants Vitaly Rodionov
2025-10-23  9:03 ` [PATCH v6 04/12] ASoC: cs530x: Correct constant naming Vitaly Rodionov
2025-10-23  9:03 ` [PATCH v6 05/12] ASoC: dt-bindings: sound: cirrus: cs530x: Add cs530x Vitaly Rodionov
2025-10-23 14:41   ` Rob Herring (Arm)
2025-10-23 18:15   ` Krzysztof Kozlowski [this message]
2025-10-23 20:57     ` Vitaly Rodionov
2025-10-23  9:03 ` [PATCH v6 06/12] ASoC: cs530x: Add CODEC and DAC support Vitaly Rodionov
2025-10-23  9:03 ` [PATCH v6 07/12] ASoC: cs530x: Rename bitfield to reflect common use for ADC and DAC Vitaly Rodionov
2025-10-23  9:03 ` [PATCH v6 08/12] ASoC: cs530x: Check the DEVID matches the devtype Vitaly Rodionov
2025-10-23  9:03 ` [PATCH v6 09/12] ASoC: cs530x: Correct MCLK reference frequency values Vitaly Rodionov
2025-10-23  9:03 ` [PATCH v6 10/12] ASoC: cs530x: Rename i2c related structures Vitaly Rodionov
2025-10-23  9:03 ` [PATCH v6 11/12] ASoC: dt-bindings: sound: cirrus: cs530x: Add SPI bus support Vitaly Rodionov
2025-10-27  8:47   ` Krzysztof Kozlowski
2025-10-23  9:03 ` [PATCH v6 12/12] ASoC: cs530x: Add SPI bus support for cs530x parts Vitaly Rodionov
2025-10-28 16:09 ` [PATCH v6 00/12] Add support for Cirrus Logic CS530x DAC and CODEC variants Mark Brown

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=fa397247-6271-47eb-bea6-ccd83808df74@kernel.org \
    --to=krzk@kernel.org \
    --cc=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