From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Peter Shen <sjg168@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>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
peter.shen@amd.com, colin.huang2@amd.com,
KKrzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [PATCH v9 1/2] dt-bindings: arm: aspeed: Add compatible for Facebook Anacapa BMC
Date: Thu, 08 Jan 2026 15:46:31 +1030 [thread overview]
Message-ID: <a9e75f46a69e86c2d555065f251b9ece3050827e.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20251219091632.1598603-2-sjg168@gmail.com>
Hi Peter,
On Fri, 2025-12-19 at 17:16 +0800, Peter Shen wrote:
> This patch adds the compatible string for the Facebook Anacapa BMC
> which uses an Aspeed AST2600 SoC. This is required before adding
> the board's device tree source file.
>
> Signed-off-by: Peter Shen <sjg168@gmail.com>
> Acked-by: KKrzysztof Kozlowski <krzk@kernel.org>
I've fixed up this tag and the misspelling of Krzysztof's name along
with it while applying the series.
It's important that you actually insert the tag provided[1] and not
invent some other one.
Please fix your workflow so this isn't a problem in the future.
I suggest using b4 (and `b4 trailers --update`) if you're not already:
https://b4.docs.kernel.org/
Andrew
[1]: https://lore.kernel.org/linux-aspeed/259e917f-0570-40d6-983f-bfe9d77444a7@kernel.org/
next prev parent reply other threads:[~2026-01-08 5:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 9:16 [PATCH v9 0/2] ARM: dts: aspeed: Add Facebook Anacapa platform Peter Shen
2025-12-19 9:16 ` [PATCH v9 1/2] dt-bindings: arm: aspeed: Add compatible for Facebook Anacapa BMC Peter Shen
2026-01-08 5:16 ` Andrew Jeffery [this message]
2025-12-19 9:16 ` [PATCH v9 2/2] ARM: dts: aspeed: Add Facebook Anacapa platform Peter Shen
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=a9e75f46a69e86c2d555065f251b9ece3050827e.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=colin.huang2@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.shen@amd.com \
--cc=robh@kernel.org \
--cc=sjg168@gmail.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