All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	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 mfd tree
Date: Wed, 19 Nov 2025 13:01:30 +0000	[thread overview]
Message-ID: <20251119130130.GS1949330@google.com> (raw)
In-Reply-To: <CAPDyKFr70C3hXyjVeoMZ2h79yyuau5E_-pZxa2txpHFZc92oOg@mail.gmail.com>

On Wed, 19 Nov 2025, Ulf Hansson wrote:

> On Tue, 18 Nov 2025 at 19:33, Lee Jones <lee@kernel.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.  :)

> 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.

Thanks buddy.  Hope that you're well.

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2025-11-19 13:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14  3:42 linux-next: duplicate patch in the mfd tree Stephen Rothwell
2025-11-18 18:33 ` Lee Jones
2025-11-19 11:57   ` Ulf Hansson
2025-11-19 13:01     ` Lee Jones [this message]
2025-11-19 17:11       ` Ulf Hansson
  -- strict thread matches above, loose matches on Subject: below --
2025-07-25  1:36 Stephen Rothwell
2025-07-25 11:35 ` Lee Jones
2025-07-25 11:48   ` Arnd Bergmann
2025-07-25 16:55     ` Sven Peter
2025-05-26  4:04 Stephen Rothwell
2025-05-30 16:44 ` Lee Jones
2025-03-17  3:45 Stephen Rothwell
2025-03-17 22:51 ` Heiko Stübner
2024-09-05  6:42 Stephen Rothwell
2024-09-09  9:07 ` Lee Jones
2023-09-25  2:14 Stephen Rothwell
2023-02-21  6:27 Stephen Rothwell
2023-01-27  5:09 Stephen Rothwell
2023-01-27  9:33 ` 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=20251119130130.GS1949330@google.com \
    --to=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=ulf.hansson@linaro.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.