linux-kernel - Re: linux-next: duplicate patch in the regulator tree

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: <7e616125-5909-41fc-a17f-21d07638d72d@sirena.org.uk>
Date: Mon, 24 Feb 2025 16:01:46 +0000
From: Mark Brown <broonie@...nel.org>
To: Shawn Guo <shawnguo2@...h.net>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
	Liam Girdwood <lgirdwood@...il.com>,
	Shawn Guo <shawnguo@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the regulator tree

On Sun, Feb 23, 2025 at 04:27:55PM +0800, Shawn Guo wrote:
> On Wed, Feb 19, 2025 at 01:43:54PM +1100, Stephen Rothwell wrote:

> > The following commit is also in the imx-mxs tree as a different commit
> > (but the same patch):

> >   b5ec74c2aec7 ("arm64: dts: imx8mp-skov-reva: Use hardware signal for SD card VSELECT")

> Any particular reason you picked this DTS change?  Would you drop it
> from regulator tree?

My understanding was that these fixes all needed to go together since
the interface changes were a bit dodgy from an ABI point of view.

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