From: "Rob Herring (Arm)" <robh@kernel.org>
To: Chanh Nguyen <chanh@os.amperecomputing.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
linux-kernel@vger.kernel.org, Joel Stanley <joel@jms.id.au>,
linux-arm-kernel@lists.infradead.org,
Quan Nguyen <quan@os.amperecomputing.com>,
Open Source Submission <patches@amperecomputing.com>,
Phong Vo <phong@os.amperecomputing.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org,
Thang Nguyen <thang@os.amperecomputing.com>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Khanh Pham <khpham@amperecomputing.com>,
linux-aspeed@lists.ozlabs.org
Subject: Re: [PATCH v2 1/2] dt-bindings: arm: aspeed: add Mt. Jefferson board
Date: Mon, 21 Oct 2024 14:50:11 -0500 [thread overview]
Message-ID: <172954021092.1028025.10007351603543504033.robh@kernel.org> (raw)
In-Reply-To: <20241021083702.9734-2-chanh@os.amperecomputing.com>
On Mon, 21 Oct 2024 08:37:01 +0000, Chanh Nguyen wrote:
> Document Ampere's Mt. Jefferson BMC board compatible.
>
> Signed-off-by: Chanh Nguyen <chanh@os.amperecomputing.com>
> ---
> Changes in v2:
> - Document Mt. Jefferson board compatible [Krzysztof]
> ---
> Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2024-10-21 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 8:37 [PATCH v2 0/2] Add device tree for Ampere's Mt. Jefferson BMC Chanh Nguyen
2024-10-21 8:37 ` [PATCH v2 1/2] dt-bindings: arm: aspeed: add Mt. Jefferson board Chanh Nguyen
2024-10-21 19:50 ` Rob Herring (Arm) [this message]
2024-10-21 8:37 ` [PATCH v2 2/2] ARM: dts: aspeed: Add device tree for Ampere's Mt. Jefferson BMC Chanh Nguyen
2024-10-21 17:58 ` [PATCH v2 0/2] " Rob Herring (Arm)
2024-10-21 23:08 ` 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=172954021092.1028025.10007351603543504033.robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=chanh@os.amperecomputing.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=khpham@amperecomputing.com \
--cc=krzk+dt@kernel.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=patches@amperecomputing.com \
--cc=phong@os.amperecomputing.com \
--cc=quan@os.amperecomputing.com \
--cc=thang@os.amperecomputing.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
all inboxes | Powered by JetHome®