From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Kelly Hung(洪嘉莉)" <Kelly_Hung@asus.com>,
"Kelly Hung" <ppighouse@gmail.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>
Cc: "krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"joel@jms.id.au" <joel@jms.id.au>,
"andrew@codeconstruct.com.au" <andrew@codeconstruct.com.au>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"AllenYY Hsu(許幼岳)" <AllenYY_Hsu@asus.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: arm: aspeed: add ASUS X4TF board
Date: Thu, 29 Feb 2024 08:56:16 +0100 [thread overview]
Message-ID: <df9c05aa-6744-4954-9918-8b2abf59bbc0@linaro.org> (raw)
In-Reply-To: <TYZPR04MB65964904A9624AF3BE05198D9D5F2@TYZPR04MB6596.apcprd04.prod.outlook.com>
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
next prev parent reply other threads:[~2024-02-29 7:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 9:29 Kelly Hung
2024-02-27 9:29 ` [PATCH v3 2/2] ARM: dts: aspeed: x4tf: Add dts for asus x4tf project Kelly Hung
2024-02-27 10:01 ` [PATCH v3 1/2] dt-bindings: arm: aspeed: add ASUS X4TF board Krzysztof Kozlowski
2024-02-29 7:45 ` Kelly Hung(洪嘉莉)
2024-02-29 7:56 ` Krzysztof Kozlowski [this message]
2024-02-27 13:45 ` Rob Herring
2024-02-29 7:13 ` Kelly Hung(洪嘉莉)
-- strict thread matches above, loose matches on Subject: below --
2024-02-27 7:50 Kelly Hung
2024-02-27 9:12 ` Krzysztof Kozlowski
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=df9c05aa-6744-4954-9918-8b2abf59bbc0@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=AllenYY_Hsu@asus.com \
--cc=Kelly_Hung@asus.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=ppighouse@gmail.com \
--cc=robh+dt@kernel.org \
/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
all inboxes | Powered by JetHome®