From: Shawn Guo <shawnguo2@yeah.net>
To: Mark Brown <broonie@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Liam Girdwood <lgirdwood@gmail.com>,
Shawn Guo <shawnguo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the regulator tree
Date: Tue, 25 Feb 2025 08:37:14 +0800 [thread overview]
Message-ID: <Z70QuuHrIbirDZiB@dragon> (raw)
In-Reply-To: <7e616125-5909-41fc-a17f-21d07638d72d@sirena.org.uk>
On Mon, Feb 24, 2025 at 04:01:46PM +0000, Mark Brown wrote:
> 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.
Let it be with regulator tree. I dropped it from imx tree.
Shawn
next prev parent reply other threads:[~2025-02-25 0:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 2:43 linux-next: duplicate patch in the regulator tree Stephen Rothwell
2025-02-23 8:27 ` Shawn Guo
2025-02-24 16:01 ` Mark Brown
2025-02-25 0:37 ` Shawn Guo [this message]
2025-02-25 13:37 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2024-07-01 5:42 Stephen Rothwell
2023-06-07 6:37 Stephen Rothwell
2023-06-07 11:29 ` Mark Brown
2023-06-08 12:42 ` Lee Jones
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=Z70QuuHrIbirDZiB@dragon \
--to=shawnguo2@yeah.net \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=shawnguo@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.