public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Mark Brown <broonie@kernel.org>
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:47:25 +0100	[thread overview]
Message-ID: <ZnLhbQmxyMJ9SAhq@opensource.cirrus.com> (raw)
In-Reply-To: <ZnLftHS7RLRRQSk/@opensource.cirrus.com>

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:
> > On Wed, Jun 19, 2024 at 02:26:36PM +0100, Charles Keepax wrote:
> > > On Wed, Jun 19, 2024 at 01:50:48PM +0100, Mark Brown wrote:
> > 
> > > > [1/2] spi: cs42l43: Refactor accessing the SDCA extension properties
> > > >       commit: 6914ee9cd1b0c91bd2fb4dbe204947c3c31259e1
> > > > [2/2] spi: cs42l43: Add speaker id support to the bridge configuration
> > > >       (no commit info)
> > 
> > > Not sure all went smoothly here. This seems to have picked up v1
> > > of the first patch and not picked up the second one.
> > 
> > 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.
> 
> I mean I can just resend it but presumably we will hit the same
> issue again.
> 

Ah I see I think your applying to the for-6.11 branch, which is
missing 60980cf5b8c8 ("spi: cs42l43: Drop cs35l56 SPI speed down
to 11MHz"). I can send a version based not on that but might make
a bit of an annoying merge conflict later?

Thanks,
Charles

  parent reply	other threads:[~2024-06-19 13:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 12:17 [PATCH v2 1/2] spi: cs42l43: Refactor accessing the SDCA extension properties 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
2024-06-19 13:47         ` Charles Keepax [this message]
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=ZnLhbQmxyMJ9SAhq@opensource.cirrus.com \
    --to=ckeepax@opensource.cirrus.com \
    --cc=broonie@kernel.org \
    --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