From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Leo Wang <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>,
Kees Cook <kees@kernel.org>, Tony Luck <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
bruce.jy.hung@fii-foxconn.com, george.kw.lee@fii-foxconn.com,
Leo Wang <leo.jt.wang@fii-foxconn.com>,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH 1/2] Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml
Date: Fri, 20 Jun 2025 15:55:44 +0930 [thread overview]
Message-ID: <8120f04c23f14ac48671a0af45838536a4600e98.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20250618-add-support-for-meta-clemente-bmc-v1-1-e5ca669ee47b@fii-foxconn.com>
Hi Leo,
The patch subject should not be the path to the affected file. Can you
please fix that? Follow the lead of other patches that have recently
touched the file.
Thanks,
Andrew
On Wed, 2025-06-18 at 17:40 +0800, Leo Wang wrote:
> Document the new compatibles used on Meta Clemente.
>
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> Signed-off-by: Leo Wang <leo.jt.wang@fii-foxconn.com>
> ---
> Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml
> b/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml
> index
> 01333ac111fbb076582a6c0e801903c3500b459f..ff3fea63cecd99ec2dc56d3cf71
> 403f897681a98 100644
> --- a/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml
> +++ b/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml
> @@ -81,6 +81,7 @@ properties:
> - asus,x4tf-bmc
> - facebook,bletchley-bmc
> - facebook,catalina-bmc
> + - facebook,clemente-bmc
> - facebook,cloudripper-bmc
> - facebook,elbert-bmc
> - facebook,fuji-bmc
>
next prev parent reply other threads:[~2025-06-20 6:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 9:40 [PATCH 0/2] ARM: dts: Add support for Meta Clemente BMC Leo Wang
2025-06-18 9:40 ` [PATCH 1/2] Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml Leo Wang
2025-06-20 6:25 ` Andrew Jeffery [this message]
2025-06-20 6:37 ` Krzysztof Kozlowski
2025-06-20 6:51 ` Geert Uytterhoeven
2025-06-18 9:40 ` [PATCH 2/2] ARM: dts: aspeed: clemente: add Meta Clemente BMC Leo Wang
2025-06-20 6:39 ` Andrew Jeffery
2025-06-18 13:36 ` [PATCH 0/2] ARM: dts: Add support for " Rob Herring (Arm)
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=8120f04c23f14ac48671a0af45838536a4600e98.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=bruce.jy.hung@fii-foxconn.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=george.kw.lee@fii-foxconn.com \
--cc=gpiccoli@igalia.com \
--cc=joel@jms.id.au \
--cc=kees@kernel.org \
--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-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
--cc=tony.luck@intel.com \
/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).