From: Mark Brown <broonie@kernel.org>
To: Fred Treven <ftreven@opensource.cirrus.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
James Ogletree <jogletre@opensource.cirrus.com>,
Ben Bright <ben.bright@cirrus.com>,
David Rhodes <david.rhodes@cirrus.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH 6/7] ASoC: cs40l26: Support I2S streaming to CS40L26
Date: Mon, 3 Feb 2025 12:23:01 +0000 [thread overview]
Message-ID: <a8a9fb40-ec8e-4e65-8de7-b9f3c708a45e@sirena.org.uk> (raw)
In-Reply-To: <20250131195639.1784933-7-ftreven@opensource.cirrus.com>
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
On Fri, Jan 31, 2025 at 01:56:37PM -0600, Fred Treven wrote:
> Introduce codec support for Cirrus Logic Device CS40L26.
>
> The ASoC driver enables I2S streaming to the device.
You've not copied me on the rest of the series so I don't know what's
going on with dependencies. When sending a patch series it is important
to ensure that all the various maintainers understand what the
relationship between the patches as the expecation is that there will be
interdependencies. Either copy everyone on the whole series or at least
copy them on the cover letter and explain what's going on. If there are
no strong interdependencies then it's generally simplest to just send
the patches separately to avoid any possible confusion.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-02-03 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250131195639.1784933-1-ftreven@opensource.cirrus.com>
2025-01-31 19:56 ` [PATCH 6/7] ASoC: cs40l26: Support I2S streaming to CS40L26 Fred Treven
2025-02-03 12:23 ` Mark Brown [this message]
2025-02-04 21:54 ` Fredrik Treven
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=a8a9fb40-ec8e-4e65-8de7-b9f3c708a45e@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ben.bright@cirrus.com \
--cc=david.rhodes@cirrus.com \
--cc=ftreven@opensource.cirrus.com \
--cc=jogletre@opensource.cirrus.com \
--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=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