From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Shen, Peter" <Peter.Shen@amd.com>,
Andrew Jeffery <andrew@codeconstruct.com.au>
Cc: Joel Stanley <joel@jms.id.au>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: arm: aspeed: Add compatible for Facebook Anacapa BMC
Date: Thu, 23 Oct 2025 09:04:44 +0200 [thread overview]
Message-ID: <a1c28952-d08f-4629-84f4-e17646f6e554@kernel.org> (raw)
In-Reply-To: <DS7PR12MB61187E5845B076BF7C7EFE0995F0A@DS7PR12MB6118.namprd12.prod.outlook.com>
On 23/10/2025 08:52, Shen, Peter wrote:
> [AMD Official Use Only - AMD Internal Distribution Only]
No, you cannot send such headers. We don't care about your corporate rules.
Also your patchset has completely broken threading.
>
> From 3129809145bd283bc52b4e105ea66d217166bb5c Mon Sep 17 00:00:00 2001
> From: Peter Shen <peter.shen@amd.com>
> Date: Thu, 23 Oct 2025 13:49:52 +0800
> Subject: [PATCH 1/2] dt-bindings: arm: aspeed: Add compatible for Facebook
> Anacapa BMC
>
> This patch adds the compatible string for the Facebook Anacapa BMC
Please do not use "This commit/patch/change", but imperative mood. See
longer explanation here:
https://elixir.bootlin.com/linux/v6.16/source/Documentation/process/submitting-patches.rst#L94
Best regards,
Krzysztof
prev parent reply other threads:[~2025-10-23 7:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 6:52 [PATCH 1/2] dt-bindings: arm: aspeed: Add compatible for Facebook Anacapa BMC Shen, Peter
2025-10-23 7:04 ` Krzysztof Kozlowski [this message]
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=a1c28952-d08f-4629-84f4-e17646f6e554@kernel.org \
--to=krzk@kernel.org \
--cc=Peter.Shen@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=robh@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;
as well as URLs for NNTP newsgroup(s).