From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rob Herring <robh@kernel.org>, Olof Johansson <olof@lixom.net>,
Arnd Bergmann <arnd@arndb.de>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul@pwsan.com>
Cc: ARM <linux-arm-kernel@lists.infradead.org>,
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: Tue, 9 Jul 2024 16:46:18 +1000 [thread overview]
Message-ID: <20240709164618.69cfcfad@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 418 bytes --]
Hi all,
The following commits are also in the arm-soc and risc-v trees as
different commits (but the same patches):
0620bce64afa ("dt-bindings: riscv: cpus: add ref to interrupt-controller")
877097a2fab0 ("dt-bindings: interrupt-controller: convert marvell,mpic binding to YAML")
c7ce06684bf5 ("dt-bindings: interrupt-controller: riscv,cpu-intc: convert to dtschema")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-07-09 6:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 6:46 Stephen Rothwell [this message]
2024-07-09 12:42 ` linux-next: duplicate patches in the devicetree tree Rob Herring
2024-07-09 13:15 ` Arnd Bergmann
2024-07-09 13:29 ` Stephen Rothwell
2024-07-09 13:34 ` Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2025-11-17 3:37 Stephen Rothwell
2025-11-17 13:41 ` Rob Herring
2025-03-21 4:38 Stephen Rothwell
2025-03-21 8:55 ` Arnd Bergmann
2024-05-15 3:01 Stephen Rothwell
2024-05-15 13:50 ` Krzysztof Wilczyński
2024-05-15 14:34 ` Rob Herring
2024-05-15 14:54 ` Krzysztof Wilczyński
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=20240709164618.69cfcfad@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=palmer@dabbelt.com \
--cc=paul@pwsan.com \
--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