linux-kernel - Re: [PATCH v2 1/2] spi: cs42l43: Refactor accessing the SDCA extension properties

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <d58879a4-a83a-4e88-9f31-e33a38e4572b@sirena.org.uk>
Date: Wed, 19 Jun 2024 14:44:29 +0100
From: Mark Brown <broonie@...nel.org>
To: Charles Keepax <ckeepax@...nsource.cirrus.com>
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: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.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)