[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZnLftHS7RLRRQSk/@opensource.cirrus.com>
Date: Wed, 19 Jun 2024 14:40:04 +0100
From: Charles Keepax <ckeepax@...nsource.cirrus.com>
To: Mark Brown <broonie@...nel.org>
CC: <linux-spi@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<patches@...nsource.cirrus.com>
Subject: Re: [PATCH v2 1/2] spi: cs42l43: Refactor accessing the SDCA
extension properties
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.
Thanks,
Charles
Powered by blists - more mailing lists