[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPDyKFqn2sKcqKQghQz=+7Ui-qfKdHRkQ910Aw7vHK9dF7NvyA@mail.gmail.com>
Date: Wed, 19 Nov 2025 18:11:22 +0100
From: Ulf Hansson <ulf.hansson@...aro.org>
To: Lee Jones <lee@...nel.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
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 mfd tree
On Wed, 19 Nov 2025 at 14:01, Lee Jones <lee@...nel.org> wrote:
>
> On Wed, 19 Nov 2025, Ulf Hansson wrote:
>
> > On Tue, 18 Nov 2025 at 19:33, Lee Jones <lee@...nel.org> wrote:
> > >
> > > On Fri, 14 Nov 2025, Stephen Rothwell wrote:
> > >
> > > > Hi all,
> > > >
> > > > The following commit is also in the pmdomain tree as a different commit
> > > > (but the same patch):
> > > >
> > > > 30ed024fb076 ("mfd: bcm2835-pm: Add support for BCM2712")
> > > >
> > > > This is commit
> > > >
> > > > 060d111e8a56 ("mfd: bcm2835-pm: Add support for BCM2712")
> > > >
> > > > in the pmdolain tree.
> > >
> > > Why is this in the pmdomain tree, Ulf?
> >
> > The corresponding dt doc patch is in my tree too, so to keep them
> > together, but also because Florian acked/suggested it to me [1].
>
> Neither of you should be deciding the fate of MFD patches. :)
Sorry, I got carried away. :-)
>
> > I can rebase and drop it from my tree, if you prefer to take it via
> > your tree? The DT doc patch is however on an immutable branch just
> > named "dt", so you need to pull that in that case. Please let me know
> > and sorry for the mess!
>
> Yes, if you can drop the MFD commit, it would solve some issues.
Done!
>
> Thanks buddy. Hope that you're well.
Np, old friend! I hope you are well too!
Kind regards
Uffe
Powered by blists - more mailing lists