From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
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@asus.com,
Allenyy_Hsu@asus.com
Subject: Re: [PATCH v6 2/2] ARM: dts: aspeed: x4tf: Add dts for asus x4tf project
Date: Tue, 26 Mar 2024 12:39:08 +0100 [thread overview]
Message-ID: <79ba66c5-a564-416d-b7bf-747422803aa6@linaro.org> (raw)
In-Reply-To: <20240326103549.2413515-3-Kelly_Hung@asus.com>
On 26/03/2024 11:35, Kelly Hung wrote:
> Base on aspeed-g6.dtsi and can boot into BMC console.
>
> Signed-off-by: Kelly Hung <Kelly_Hung@asus.com>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
That's not true.
Please provide a link to lore.kernel.org which will prove that you
received this tag.
> Reviewed-by: Andrew Jeffery <andrew@codeconstruct.com.au>
Please provide a link to lore.kernel.org which will prove that you
received this tag.
Did you read the documentation I was sharing with you?
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-03-26 11:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 10:35 [PATCH v6 0/2] Add Reviewed-by and Acked-by tags Kelly Hung
2024-03-26 10:35 ` [PATCH v6 1/2] dt-bindings: arm: aspeed: add ASUS X4TF board Kelly Hung
2024-03-26 11:36 ` Krzysztof Kozlowski
2024-03-26 18:24 ` Conor Dooley
2024-04-30 1:28 ` Andrew Jeffery
2024-03-26 10:35 ` [PATCH v6 2/2] ARM: dts: aspeed: x4tf: Add dts for asus x4tf project Kelly Hung
2024-03-26 11:39 ` Krzysztof Kozlowski [this message]
2024-03-27 1:46 ` [PATCH v6 0/2] Add Reviewed-by and Acked-by tags Andrew Jeffery
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=79ba66c5-a564-416d-b7bf-747422803aa6@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Allenyy_Hsu@asus.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=kelly_hung@asus.com \
--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