From: "Arnd Bergmann" <arnd@arndb.de>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"Rob Herring" <robh@kernel.org>
Cc: ARM <linux-arm-kernel@lists.infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the devicetree tree
Date: Fri, 21 Mar 2025 09:55:17 +0100 [thread overview]
Message-ID: <1eda0df7-a797-43b9-b3d0-3d1855b58e38@app.fastmail.com> (raw)
In-Reply-To: <20250321153800.639f03c5@canb.auug.org.au>
On Fri, Mar 21, 2025, at 05:38, Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in the arm-soc tree as different commits
> (but the same patches):
>
> a78f7a337bc7 ("docs: process: maintainer-soc-clean-dts: linux-next is
> decisive")
> b31cc6af1bb1 ("docs: dt: submitting-patches: Document sending DTS
> patches")
>
> These are commits
>
> a42d2d53a6d7 ("docs: process: maintainer-soc-clean-dts: linux-next is
> decisive")
> d98d35d99e0f ("docs: dt: submitting-patches: Document sending DTS
> patches")
>
> in the arm-soc tree.
My mistake, I saw them in the patchwork backlog and applied them.
I dropped them again now as they were still on the top of my branch.
Arnd
next prev parent reply other threads:[~2025-03-21 8:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 4:38 linux-next: duplicate patches in the devicetree tree Stephen Rothwell
2025-03-21 8:55 ` Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-17 3:37 Stephen Rothwell
2025-11-17 13:41 ` Rob Herring
2024-07-09 6:46 Stephen Rothwell
2024-07-09 12:42 ` Rob Herring
2024-07-09 13:15 ` Arnd Bergmann
2024-07-09 13:29 ` Stephen Rothwell
2024-07-09 13:34 ` Rob Herring
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=1eda0df7-a797-43b9-b3d0-3d1855b58e38@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robh@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