From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patches in the devicetree tree
Date: Wed, 15 May 2024 13:01:39 +1000 [thread overview]
Message-ID: <20240515130139.2da899c0@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
Hi all,
The following commits are also in the pci tree as different commits
(but the same patches):
15be4f7ce5de ("dt-bindings: Drop unnecessary quotes on keys")
28081ebd17fb ("dt-bindings: PCI: qcom,pcie-sm8350: Drop redundant 'oneOf' sub-schema")
649bad67d4b1 ("dt-bindings: PCI: microchip: increase number of items in ranges property")
These are commits
d7890a80e037 ("dt-bindings: Drop unnecessary quotes on keys")
301e978b9eb7 ("dt-bindings: PCI: qcom,pcie-sm8350: Drop redundant 'oneOf' sub-schema")
247edade4b4b ("dt-bindings: PCI: microchip: Increase number of items in ranges property")
in the pci tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-05-15 3:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 3:01 Stephen Rothwell [this message]
2024-05-15 13:50 ` linux-next: duplicate patches in the devicetree tree Krzysztof Wilczyński
2024-05-15 14:34 ` Rob Herring
2024-05-15 14:54 ` Krzysztof Wilczyński
-- strict thread matches above, loose matches on Subject: below --
2024-01-21 9:33 Stephen Rothwell
2023-12-18 5:42 Stephen Rothwell
2023-12-18 14:07 ` Rob Herring
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=20240515130139.2da899c0@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--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=robh@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).