linux-kernel - Re: [PATCH v3 12/13] arm64: dts: renesas: Add initial support for renesas RZ/T2H eval board

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: <ac45cb5e-d991-4962-9c0a-02496be1af75@kernel.org>
Date: Wed, 26 Feb 2025 16:13:30 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Paul Barker <paul.barker.ct@...renesas.com>,
 Thierry Bultel <thierry.bultel.yh@...renesas.com>, thierry.bultel@...atsea.fr
Cc: linux-renesas-soc@...r.kernel.org, geert@...ux-m68k.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 12/13] arm64: dts: renesas: Add initial support for
 renesas RZ/T2H eval board

On 26/02/2025 15:46, Paul Barker wrote:
> On 26/02/2025 14:23, Krzysztof Kozlowski wrote:
>> On 26/02/2025 14:09, Thierry Bultel wrote:
>>> Add the initial device tree for the RZ/T2H evaluation board.
>>>
>>> Signed-off-by: Thierry Bultel <thierry.bultel.yh@...renesas.com>
>>> Reviewed-by: Paul Barker <paul.barker.ct@...renesas.com>
>>
>> Where did this happen? I see tags only to few patches, not all of them.
>>
>> Same questions for all other places.
>>
>> Best regards,
>> Krzysztof
> 
> Hi Krzysztof,
> 
> We've recently switched to a patchwork instance and internal mailing
> list for review within our team before sending things to the mailing
> list. We did a round of internal review and the Reviewed-by tags from
> this have accidentally been included here. It can easily be fixed.
> 
> Thierry, could you re-send a v4 series keeping my Reviewed-by tag only
> on patch 7/13, as that was added on the public mailing list.


Thanks for clarification. It is unusual to see internal review resulting
in tags between already publicly discussed versions. Why it cannot be
done in public where everything is both archived and visible to entire
community?

BTW, sometimes b4 makes mistakes and we already have at least two cases
tag from one patch was applied for entire set, so your case is
indistinguishable from such b4 issue.

Best regards,
Krzysztof