From: Conor Dooley <conor@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "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 23:58:38 +0100 [thread overview]
Message-ID: <20240514-nerd-acclaim-04cf23e62926@spud> (raw)
In-Reply-To: <20240515083145.5ef498a0@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
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.
Cheers,
Conor.
>
> These are commits
>
> 6e12a52c1459 ("dt-bindings: gpio: mpfs: add coreGPIO support")
> f752a52d34cb ("dt-bindings: gpio: mpfs: allow gpio-line-names")
>
> in Linus' tree.
>
> --
> Cheers,
> Stephen Rothwell
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-05-14 22:58 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 [this message]
2024-05-14 23:27 ` Bjorn Helgaas
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=20240514-nerd-acclaim-04cf23e62926@spud \
--to=conor@kernel.org \
--cc=bhelgaas@google.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox