From: Krzysztof Kozlowski <krzk@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Arnd Bergmann <arnd@arndb.de>
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: Re: linux-next: duplicate patch in the dt-krzk tree
Date: Mon, 12 May 2025 08:34:19 +0200 [thread overview]
Message-ID: <2006c4aa-7d4e-48de-9c27-46ddb359ac48@kernel.org> (raw)
In-Reply-To: <20250512145955.617fd207@canb.auug.org.au>
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.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-12 6:34 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 [this message]
2025-05-12 6:43 ` Arnd Bergmann
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=2006c4aa-7d4e-48de-9c27-46ddb359ac48@kernel.org \
--to=krzk@kernel.org \
--cc=arnd@arndb.de \
--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