linux-kernel - Re: [PATCH v5 0/2] ARM: dts: aspeed: Add Device Tree for Facebook Anacapa BMC

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: <20dbf272-b5a0-4fc6-b5c7-54fdaa05173d@kernel.org>
Date: Fri, 7 Nov 2025 09:38:18 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Peter Shen <sjg168@...il.com>
Cc: Andrew Jeffery <andrew@...econstruct.com.au>,
 Joel Stanley <joel@....id.au>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, devicetree@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, linux-aspeed@...ts.ozlabs.org,
 linux-kernel@...r.kernel.org, peter.shen@....com
Subject: Re: [PATCH v5 0/2] ARM: dts: aspeed: Add Device Tree for Facebook
 Anacapa BMC

On 07/11/2025 09:22, Peter Shen wrote:
> This patch series adds the device tree binding and the initial device tree
> source file for the Facebook Anacapa BMC, which utilizes the Aspeed AST2600
> SoC.
> 
> The patches configure the necessary platform peripherals and aliases for
> OpenBMC usage.
> 
> ---
> Changes in v5:
> - Fixed the final DCO mismatch (Broken DCO/email chain). The email sender address (From:) is now corrected to fully match the Signed-off-by: and Author: address (sjg168@...il.com) to comply with DCO rules.
> 
> - (V4 Changelog) Corrected all previous style issues: fixed block comment styles, line length issues, and removed un-documented/unused device tree nodes (amd,helios_cpld and eeprom@53).

Please stop. You already sent v4, then immediately v5. All patches are
missing and cover letters are incorrectly threaded.

Can you please slow down and look at commands you are typing (e.g. look
in manual for explanation of --dry-run).

Do not attach (thread) your patchsets to some other threads (unrelated
or older versions). This buries them deep in the mailbox and might
interfere with applying entire sets. See also:
https://elixir.bootlin.com/linux/v6.16-rc2/source/Documentation/process/submitting-patches.rst#L830


Best regards,
Krzysztof