From: Lee Jones <lee@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Maciej Strozek <mstrozek@opensource.cirrus.com>,
Takashi Iwai <tiwai@suse.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Jaroslav Kysela <perex@perex.cz>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
patches@opensource.cirrus.com, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 RESEND 3/4] mfd: cs42l43: Add support for the B variant
Date: Fri, 6 Mar 2026 13:58:25 +0000 [thread overview]
Message-ID: <20260306135825.GO183676@google.com> (raw)
In-Reply-To: <a141da68-35a7-491e-bb6f-ca9b448030ff@sirena.org.uk>
On Mon, 02 Mar 2026, Mark Brown wrote:
> On Fri, Feb 27, 2026 at 01:01:00PM +0000, Maciej Strozek wrote:
> > Introducing CS42L43B codec, a variant of CS42L43 which can be driven by
> > the same driver.
>
> Lee, this seems like it's mostly an ASoC series - does it make sense for
> me to apply this along with everything else and send a tag (assuming
> it's OK of course, I just scanned this patch very quickly rather than
> reviewing it)?
Yes, that's fine.
Acked-by: Lee Jones <lee@kernel.org>
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2026-03-06 13:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 13:00 [PATCH v4 RESEND 0/4] Add support for CS42L43B codec to CS42L43 driver Maciej Strozek
2026-02-27 13:00 ` [PATCH v4 RESEND 1/4] ASoC: sdw_utils: Add CS42L43B codec info Maciej Strozek
2026-02-27 13:00 ` [PATCH v4 RESEND 2/4] ASoC: dt-bindings: cirrus,cs42l43: Add CS42L43B variant Maciej Strozek
2026-02-27 13:01 ` [PATCH v4 RESEND 3/4] mfd: cs42l43: Add support for the B variant Maciej Strozek
2026-03-02 21:07 ` Mark Brown
2026-03-06 13:58 ` Lee Jones [this message]
2026-02-27 13:01 ` [PATCH v4 RESEND 4/4] ASoC: " Maciej Strozek
2026-03-06 14:53 ` Charles Keepax
2026-03-09 23:22 ` [PATCH v4 RESEND 0/4] Add support for CS42L43B codec to CS42L43 driver 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=20260306135825.GO183676@google.com \
--to=lee@kernel.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mstrozek@opensource.cirrus.com \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.