linux-kernel - Re: linux-next: duplicate patch in the dt-krzk tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <f52571c5-2d26-41cd-9266-21433423ba73@app.fastmail.com>
Date: Mon, 12 May 2025 08:43:33 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Krzysztof Kozlowski" <krzk@...nel.org>,
 "Stephen Rothwell" <sfr@...b.auug.org.au>
Cc: ARM <linux-arm-kernel@...ts.infradead.org>,
 "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
 linux-next <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the dt-krzk tree

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@...ts.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