From: Krzysztof Kozlowski <krzk@kernel.org>
To: Rajaganesh Rathinasabapathi <Rajaganesh.Rathinasabapathi@amd.com>,
devicetree@vger.kernel.org, openbmc@lists.ozlabs.org,
joel@jms.id.au, andrew@codeconstruct.com.au
Cc: robh+dt@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: arm: aspeed: Add AMD Onyx BMC compatible
Date: Tue, 18 Mar 2025 17:43:41 +0100 [thread overview]
Message-ID: <1142f61a-63d8-4a3c-8f89-a7b3bbd6cdc9@kernel.org> (raw)
In-Reply-To: <20250318041224.1693323-1-Rajaganesh.Rathinasabapathi@amd.com>
On 18/03/2025 05:12, Rajaganesh Rathinasabapathi wrote:
> Document new AMD Onyx BMC board compatibles
>
> Signed-off-by: Rajaganesh Rathinasabapathi <Rajaganesh.Rathinasabapathi@amd.com>
> ---
> Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-18 16:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 4:12 [PATCH v3 1/2] dt-bindings: arm: aspeed: Add AMD Onyx BMC compatible Rajaganesh Rathinasabapathi
2025-03-18 4:12 ` [PATCH v3 2/2] ARM:dts:aspeed: Initial device tree for AMD Onyx Platform Rajaganesh Rathinasabapathi
2025-03-18 8:45 ` Krzysztof Kozlowski
2025-03-18 16:44 ` Rajaganesh Rathinasabapathi
2025-03-18 16:58 ` Krzysztof Kozlowski
2025-03-18 14:08 ` Andrew Lunn
2025-03-18 16:48 ` Rajaganesh Rathinasabapathi
2025-03-18 16:54 ` Andrew Lunn
2025-03-18 8:44 ` [PATCH v3 1/2] dt-bindings: arm: aspeed: Add AMD Onyx BMC compatible Krzysztof Kozlowski
2025-03-18 16:42 ` Rajaganesh Rathinasabapathi
2025-03-18 16:43 ` Krzysztof Kozlowski
2025-03-18 16:43 ` Krzysztof Kozlowski [this message]
2025-03-18 17:07 ` 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=1142f61a-63d8-4a3c-8f89-a7b3bbd6cdc9@kernel.org \
--to=krzk@kernel.org \
--cc=Rajaganesh.Rathinasabapathi@amd.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--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=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