From: Bjorn Helgaas <helgaas@kernel•org>
To: Conor Dooley <conor@kernel•org>
Cc: "Stephen Rothwell" <sfr@canb•auug.org.au>,
"Bjorn Helgaas" <bhelgaas@google•com>,
"Lorenzo Pieralisi" <lpieralisi@kernel•org>,
"Krzysztof Wilczyński" <kw@linux•com>,
"Linux Kernel Mailing List" <linux-kernel@vger•kernel.org>,
"Linux Next Mailing List" <linux-next@vger•kernel.org>
Subject: Re: linux-next: duplicate patches in the pci tree
Date: Tue, 14 May 2024 18:27:46 -0500 [thread overview]
Message-ID: <20240514232746.GA2089475@bhelgaas> (raw)
In-Reply-To: <20240514-nerd-acclaim-04cf23e62926@spud>
On Tue, May 14, 2024 at 11:58:38PM +0100, Conor Dooley wrote:
> On Wed, May 15, 2024 at 08:31:45AM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > The following commits are also in Linus Torvalds' tree as different
> > commits (but the same patches):
> >
> > 8b77e887b96c ("dt-bindings: gpio: mpfs: Add coreGPIO support")
> > 8c24b6f1709f ("dt-bindings: gpio: mpfs: Allow gpio-line-names")
>
> Neither of these, nor commit ff26bed00278 ("dt-bindings: riscv:
> microchip: Document beaglev-fire") should be in the PCI tree really.
>
> ff26bed00278 ("dt-bindings: riscv: microchip: Document beaglev-fire")
> I don't mind if the PCI tree takes though, I didn't apply it for this
> cycle so there shouldn't be a clash there.
Hmmm, yeah. I think we should drop these from the PCI tree:
ff26bed00278 ("dt-bindings: riscv: microchip: Document beaglev-fire")
8b77e887b96c ("dt-bindings: gpio: mpfs: Add coreGPIO support")
8c24b6f1709f ("dt-bindings: gpio: mpfs: Allow gpio-line-names")
There's no obvious PCI connection for any of those.
Krzysztof, can you drop them from pci/dt-bindings?
> > These are commits
> >
> > 6e12a52c1459 ("dt-bindings: gpio: mpfs: add coreGPIO support")
> > f752a52d34cb ("dt-bindings: gpio: mpfs: allow gpio-line-names")
> >
> > in Linus' tree.
next prev parent reply other threads:[~2024-05-14 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 22:31 linux-next: duplicate patches in the pci tree Stephen Rothwell
2024-05-14 22:58 ` Conor Dooley
2024-05-14 23:27 ` Bjorn Helgaas [this message]
2024-05-15 13:53 ` Krzysztof Wilczyński
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=20240514232746.GA2089475@bhelgaas \
--to=helgaas@kernel$(echo .)org \
--cc=bhelgaas@google$(echo .)com \
--cc=conor@kernel$(echo .)org \
--cc=kw@linux$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lpieralisi@kernel$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox