[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240515135305.GB450088@rocinante>
Date: Wed, 15 May 2024 22:53:05 +0900
From: Krzysztof WilczyĆski <kw@...ux.com>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: Conor Dooley <conor@...nel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Lorenzo Pieralisi <lpieralisi@...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 patches in the pci tree
Hello,
> > > 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?
Done.
With some of the DT patches, I am not always sure who will be taking them,
and so to err on the side of making sure that things are included, I will
pick some of these up.
Krzysztof
Powered by blists - more mailing lists