linux-kernel - Re: [PATCH v3 1/2] dt-bindings: arm: aspeed: add ASUS X4TF 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: <df9c05aa-6744-4954-9918-8b2abf59bbc0@linaro.org>
Date: Thu, 29 Feb 2024 08:56:16 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Kelly Hung(洪嘉莉) <Kelly_Hung@...s.com>,
 Kelly Hung <ppighouse@...il.com>, "robh+dt@...nel.org" <robh+dt@...nel.org>
Cc: "krzysztof.kozlowski+dt@...aro.org" <krzysztof.kozlowski+dt@...aro.org>,
 "conor+dt@...nel.org" <conor+dt@...nel.org>, "joel@....id.au"
 <joel@....id.au>, "andrew@...econstruct.com.au"
 <andrew@...econstruct.com.au>,
 "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
 "linux-arm-kernel@...ts.infradead.org"
 <linux-arm-kernel@...ts.infradead.org>,
 "linux-aspeed@...ts.ozlabs.org" <linux-aspeed@...ts.ozlabs.org>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
 "openbmc@...ts.ozlabs.org" <openbmc@...ts.ozlabs.org>,
 AllenYY Hsu(許幼岳) <AllenYY_Hsu@...s.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: arm: aspeed: add ASUS X4TF board

On 29/02/2024 08:45, Kelly Hung(洪嘉莉) wrote:
> Hi, Krzysztof,
> 
> I correct my change log
>> Document the new compatibles used on ASUS X4TF.
>>
>> Changelog
>> Changes in v3
>> --- The new compatible is a BMC for a ASUS X4TF server which use a ast2600-a3 chip, so correct string to asus,x4tf-bmc
> 
> Do I need to resend v3 patch again with the correct change log?

You need to send v4 with correct changelog and tags.

https://elixir.bootlin.com/linux/v6.5-rc3/source/Documentation/process/submitting-patches.rst#L577

If a tag was not added on purpose, please state why and what changed.

Best regards,
Krzysztof