From: Krzysztof Kozlowski <krzk@kernel.org>
To: Peter Shen <sjg168@gmail.com>, devicetree@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Joel Stanley <joel@jms.id.au>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
peter.shen@amd.com
Subject: Re: [PATCH v7 1/2] dt-bindings: arm: aspeed: Add compatible for Facebook Anacapa BMC
Date: Tue, 18 Nov 2025 08:21:50 +0100 [thread overview]
Message-ID: <c061ee38-5026-497d-b757-b0b9db2e6729@kernel.org> (raw)
In-Reply-To: <20251118041058.1342672-2-sjg168@gmail.com>
On 18/11/2025 05:10, 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>
> ---
> Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml | 1 +
> 1 file changed, 1 insertion(+)
So you just ignored everything I wrote? Long explanation and you just
don't care?
If so, then:
NAK,
Also, do not attach (thread) your patchsets to some other threads
(unrelated or older versions). This buries them deep in the mailbox and
might interfere with applying entire sets. See also:
https://elixir.bootlin.com/linux/v6.16-rc2/source/Documentation/process/submitting-patches.rst#L830
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-18 7:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 21:12 [PATCH v6 0/2] ARM: dts: aspeed: Add Device Tree for Facebook Anacapa BMC Peter Shen
2025-11-12 21:12 ` [PATCH v6 1/2] dt-bindings: arm: aspeed: Add compatible " Peter Shen
2025-11-13 7:14 ` Krzysztof Kozlowski
2025-11-12 21:12 ` [PATCH v6 2/2] ARM: dts: aspeed: Add Device Tree " Peter Shen
2025-11-14 4:28 ` Andrew Jeffery
2025-11-14 4:30 ` [PATCH v6 0/2] " Andrew Jeffery
2025-11-18 4:10 ` [PATCH v7 " Peter Shen
2025-11-18 4:10 ` [PATCH v7 1/2] dt-bindings: arm: aspeed: Add compatible " Peter Shen
2025-11-18 7:21 ` Krzysztof Kozlowski [this message]
2025-11-18 8:11 ` Peter Shen
2025-11-18 4:10 ` [PATCH v7 2/2] ARM: dts: aspeed: Add Device Tree " 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=c061ee38-5026-497d-b757-b0b9db2e6729@kernel.org \
--to=krzk@kernel.org \
--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=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;
as well as URLs for NNTP newsgroup(s).