From: Krzysztof Kozlowski <krzk@kernel.org>
To: leo.jt.wang@gmail.com, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
george.kw.lee@fii-foxconn.com, leo.jt.wang@fii-foxconn.com
Subject: Re: [PATCH 2/2] ARM: dts: aspeed: clemente: add Meta Clemente BMC
Date: Tue, 13 May 2025 09:44:30 +0200 [thread overview]
Message-ID: <cb1e6cb8-2d51-44b5-88a6-8015a011380b@kernel.org> (raw)
In-Reply-To: <6822b851.050a0220.27a24d.d071@mx.google.com>
On 13/05/2025 05:10, leo.jt.wang@gmail.com wrote:
> From: Leo Wang <leo.jt.wang@fii-foxconn.com>
>
> Add linux device tree entry for Meta Clemente compute-tray
> BMC using AST2600 SoC.
>
> Signed-off-by: Leo Wang <leo.jt.wang@fii-foxconn.com>
Missing threading.
Missing versioning.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-13 7:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250513031010.267994-1-LeoWang>
2025-05-13 3:10 ` [PATCH 2/2] ARM: dts: aspeed: clemente: add Meta Clemente BMC leo.jt.wang
2025-05-13 7:44 ` Krzysztof Kozlowski [this message]
2025-05-13 12:38 ` Andrew Lunn
2025-05-14 6:45 ` [PATCH V2 " leo.jt.wang
2025-05-14 13:11 ` [PATCH " Rob Herring (Arm)
2025-05-26 10:01 ` [PATCH V3 " leo.jt.wang
2025-05-26 12:50 ` Krzysztof Kozlowski
2025-05-27 15:11 ` [PATCH v4 " leo.jt.wang
2025-05-27 17:56 ` [PATCH V3 " Rob Herring (Arm)
2025-06-18 9:40 [PATCH 0/2] ARM: dts: Add support for " Leo Wang
2025-06-18 9:40 ` [PATCH 2/2] ARM: dts: aspeed: clemente: add " Leo Wang
2025-06-20 6:39 ` 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=cb1e6cb8-2d51-44b5-88a6-8015a011380b@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=george.kw.lee@fii-foxconn.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=leo.jt.wang@fii-foxconn.com \
--cc=leo.jt.wang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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 NNTP newsgroup(s).