From: Fredrik Treven <ftreven@opensource.cirrus.com>
To: Mark Brown <broonie@kernel.org>
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: Tue, 4 Feb 2025 15:54:28 -0600 [thread overview]
Message-ID: <2112e5e6-618b-41d3-ba8d-168d4a72f501@opensource.cirrus.com> (raw)
In-Reply-To: <a8a9fb40-ec8e-4e65-8de7-b9f3c708a45e@sirena.org.uk>
On 2/3/25 06:23, Mark Brown wrote:
> 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.
Thanks for catching this, Mark. I made a mistake when sending the email
since the patchset touches multiple subsystems. I accidentally only
sent each patch to the maintainers of that specific subsystem rather
than grouping them all together. I will do a resend to correct this.
Best regards,
Fred
next prev parent reply other threads:[~2025-02-04 21:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250131195639.1784933-1-ftreven@opensource.cirrus.com>
2025-01-31 19:56 ` [PATCH 1/7] firmware: cs_dsp: Fix error checking in wseq_write() Fred Treven
2025-02-02 17:34 ` Markus Elfring
2025-02-04 10:03 ` Charles Keepax
2025-01-31 19:56 ` [PATCH 2/7] firmware: cs_dsp: Check for valid num_regs in cs_dsp_wseq_multi_write() Fred Treven
2025-02-04 10:06 ` Charles Keepax
2025-02-04 21:51 ` Fredrik Treven
2025-01-31 19:56 ` [PATCH 3/7] firmware: cs_dsp: Add ability to load multiple coefficient files Fred Treven
2025-02-04 10:10 ` Charles Keepax
2025-02-04 22:05 ` Fredrik Treven
2025-01-31 19:56 ` [PATCH 4/7] dt-bindings: mfd: cirrus,cs40l26: Support for CS40L26 Fred Treven
2025-02-02 14:04 ` Krzysztof Kozlowski
2025-02-04 22:18 ` Fredrik Treven
2025-02-05 7:29 ` Krzysztof Kozlowski
2025-01-31 19:56 ` [PATCH 5/7] mfd: cs40l26: Add support for CS40L26 core driver Fred Treven
2025-01-31 19:56 ` [PATCH 6/7] ASoC: cs40l26: Support I2S streaming to CS40L26 Fred Treven
2025-02-03 12:23 ` Mark Brown
2025-02-04 21:54 ` Fredrik Treven [this message]
2025-01-31 19:56 ` [PATCH 7/7] Input: cs40l26 - Add support for CS40L26 haptic driver Fred 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=2112e5e6-618b-41d3-ba8d-168d4a72f501@opensource.cirrus.com \
--to=ftreven@opensource.cirrus.com \
--cc=ben.bright@cirrus.com \
--cc=broonie@kernel.org \
--cc=david.rhodes@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 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.