From: "Arnd Bergmann" <arnd@arndb.de>
To: "Krzysztof Kozlowski" <krzk@kernel.org>,
"Stephen Rothwell" <sfr@canb.auug.org.au>
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 patch in the dt-krzk tree
Date: Mon, 12 May 2025 08:43:33 +0200 [thread overview]
Message-ID: <f52571c5-2d26-41cd-9266-21433423ba73@app.fastmail.com> (raw)
In-Reply-To: <2006c4aa-7d4e-48de-9c27-46ddb359ac48@kernel.org>
On Mon, May 12, 2025, at 08:34, Krzysztof Kozlowski wrote:
> On 12/05/2025 06:59, Stephen Rothwell wrote:
>> Hi all,
>>
>> The following commit is also in the arm-soc tree as a different commit
>> (but the same patch):
>>
>> b112d9ffaa65 ("ARM: dts: vt8500: use correct ohci/ehci node names")
>>
>> This is commit
>>
>> 7dc891191e64 ("ARM: dts: vt8500: use correct ohci/ehci node names")
>
> I will drop mine, but I am surprised that this patch appeared in
> arm-soc. soc@ was not Cced on the patchset.
My mistake. I think what happened was that patch 0/5 and 3/5
(the one for spear) of the series were sent to soc@lists.linux.dev:
https://lore.kernel.org/soc/20250330193833.21970-7-wsa+renesas@sang-engineering.com/T/#t
I had some problems with patchwork recently and picked up some of
the missing bits through b4, which always applies the entire
series. I made sure that the patch themselves were ok and I saw
your Reviewed-by tag, but I didn't realize that I was not the
recipient for patches 1, 2, 4 and 5.
Arnd
prev parent reply other threads:[~2025-05-12 6:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 4:59 linux-next: duplicate patch in the dt-krzk tree Stephen Rothwell
2025-05-12 6:34 ` Krzysztof Kozlowski
2025-05-12 6:43 ` Arnd Bergmann [this message]
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=f52571c5-2d26-41cd-9266-21433423ba73@app.fastmail.com \
--to=arnd@arndb.de \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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