From: Ricardo Rivera-Matos <rriveram@opensource.cirrus.com>
To: Mark Brown <broonie@kernel.org>
Cc: David Rhodes <david.rhodes@cirrus.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-sound@vger.kernel.org, patches@opensource.cirrus.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Introduces MDSYNC support for CS35L45
Date: Fri, 21 Aug 2026 13:26:15 -0500 [thread overview]
Message-ID: <e21671ee-860f-448a-b669-7a9820fff8a5@opensource.cirrus.com> (raw)
In-Reply-To: <536cf599-5c62-4248-8962-45ee4be48d80@sirena.org.uk>
On 8/21/26 11:23 AM, Mark Brown wrote:
> On Fri, Aug 21, 2026 at 04:09:44PM +0000, Ricardo Rivera-Matos wrote:
>> The CS35L45 has SYNC pin that can be used as a multi
>> device synchronization (MDSYNC) bus. This pin can send
>> various message types between Cirrus devices.
>
> Something is broken with how you're posting your patches which
> consistently causes your cover letter to appear as the last message in
> the series rather than the first. Not sure what's up with that, haven't
> seen other people with similar issues.
>
> You might want to look at b4 to send the patches, especially it's web
> submission endpoint which avoids having to configure mail:
>
> https://b4.docs.kernel.org/en/latest/contributor/overview.html
>
Thanks for the tip. I'll give it a shot on v4.
prev parent reply other threads:[~2026-08-21 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 16:09 [PATCH v3 1/2] ASoC: dt-bindings: cs35l45: Adds SYNC properties Ricardo Rivera-Matos
2026-08-21 16:09 ` [PATCH v3 2/2] ASoC: cs35l45: Adds support for SYNC bus Ricardo Rivera-Matos
2026-08-21 16:09 ` [PATCH v3 0/2] Introduces MDSYNC support for CS35L45 Ricardo Rivera-Matos
2026-08-21 16:23 ` Mark Brown
2026-08-21 18:26 ` Ricardo Rivera-Matos [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=e21671ee-860f-448a-b669-7a9820fff8a5@opensource.cirrus.com \
--to=rriveram@opensource.cirrus.com \
--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=rf@opensource.cirrus.com \
--cc=robh@kernel.org \
/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