From: "Kelly Hung(洪嘉莉)" <Kelly_Hung@asus.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Kelly Hung <ppighouse@gmail.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"joel@jms.id.au" <joel@jms.id.au>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"AllenYY Hsu(許幼岳)" <AllenYY_Hsu@asus.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH v3 1/2] dt-bindings: arm: aspeed: add ASUS X4TF board
Date: Thu, 29 Feb 2024 07:45:49 +0000 [thread overview]
Message-ID: <TYZPR04MB65964904A9624AF3BE05198D9D5F2@TYZPR04MB6596.apcprd04.prod.outlook.com> (raw)
In-Reply-To: <60d048df-9a54-4239-8a8b-a8eb9a59dde9@linaro.org>
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?
Thanks for review.
Best Regards
Kelly
-----Original Message-----
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Sent: Tuesday, February 27, 2024 6:02 PM
To: Kelly Hung <ppighouse@gmail.com>; robh+dt@kernel.org
Cc: krzysztof.kozlowski+dt@linaro.org; conor+dt@kernel.org; joel@jms.id.au; andrew@codeconstruct.com.au; devicetree@vger.kernel.org; linux-arm-kernel@lists.infradead.org; linux-aspeed@lists.ozlabs.org; linux-kernel@vger.kernel.org; openbmc@lists.ozlabs.org; Kelly Hung(洪嘉莉) <Kelly_Hung@asus.com>; AllenYY Hsu(許幼岳) <AllenYY_Hsu@asus.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: arm: aspeed: add ASUS X4TF board
External email : Ensure your email is secure before opening links and attachments.
On 27/02/2024 10:29, Kelly Hung wrote:
> Document the new compatibles used on ASUS X4TF.
>
> Changelog
> Changes in v3
> - correct string to asus,x4tf-bmc
Changelog goes after ---.
Again: what happened with the tags? Why aren't you responding to comments you receive?
Best regards,
Krzysztof
<p></p>
===================================================================================================================================
This email and any attachments to it contain confidential information and are intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient or receive it accidentally, please immediately notify the sender by e-mail and delete the message and any attachments from your computer system, and destroy all hard copies. Please be advised that any unauthorized disclosure, copying, distribution or any action taken or omitted in reliance on this, is illegal and prohibited. Any views or opinions expressed are solely those of the author and do not represent those of ASUSTeK.
For pricing information, ASUS is only entitled to set a recommendation resale price. All customers are free to set their own price as they wish.
===================================================================================================================================
next prev parent reply other threads:[~2024-02-29 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 9:29 [PATCH v3 1/2] dt-bindings: arm: aspeed: add ASUS X4TF board 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 13:45 ` [PATCH v3 1/2] dt-bindings: arm: aspeed: add ASUS X4TF board Rob Herring
2024-02-29 7:13 ` Kelly Hung(洪嘉莉)
[not found] ` <60d048df-9a54-4239-8a8b-a8eb9a59dde9@linaro.org>
2024-02-29 7:45 ` Kelly Hung(洪嘉莉) [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-27 7:50 Kelly Hung
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=TYZPR04MB65964904A9624AF3BE05198D9D5F2@TYZPR04MB6596.apcprd04.prod.outlook.com \
--to=kelly_hung@asus.com \
--cc=AllenYY_Hsu@asus.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).