From: Mark Brown <broonie@kernel.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH v2 1/2] spi: cs42l43: Refactor accessing the SDCA extension properties
Date: Wed, 19 Jun 2024 14:44:29 +0100 [thread overview]
Message-ID: <d58879a4-a83a-4e88-9f31-e33a38e4572b@sirena.org.uk> (raw)
In-Reply-To: <ZnLftHS7RLRRQSk/@opensource.cirrus.com>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
On Wed, Jun 19, 2024 at 02:40:04PM +0100, Charles Keepax wrote:
> On Wed, Jun 19, 2024 at 02:30:33PM +0100, Mark Brown wrote:
> > That's because when I told you that the second patch didn't apply I left
> > the other one in the queue, and what you sent now didn't apply either.
> Hmm... what branch are you applying this to? Pulling the patch
> off the list and git am-ing it onto your spi for-next branch
> works fine for me.
Nothing gets applied to for-next or for-linus, they get applied to the
version specific branches or sometimes a topic branch. Those two
branches are constantly regenerated merges.
> I mean I can just resend it but presumably we will hit the same
> issue again.
I didn't mail you yet because I didn't look at trying to figure out what
it might apply to.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-06-19 13:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 12:17 Charles Keepax
2024-06-19 12:17 ` [PATCH v2 2/2] spi: cs42l43: Add speaker id support to the bridge configuration Charles Keepax
2024-06-19 12:50 ` [PATCH v2 1/2] spi: cs42l43: Refactor accessing the SDCA extension properties Mark Brown
2024-06-19 13:26 ` Charles Keepax
2024-06-19 13:30 ` Mark Brown
2024-06-19 13:40 ` Charles Keepax
2024-06-19 13:44 ` Mark Brown [this message]
2024-06-19 13:47 ` Charles Keepax
2024-06-19 13:56 ` 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=d58879a4-a83a-4e88-9f31-e33a38e4572b@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=patches@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
all inboxes | Powered by JetHome®