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,
jothayot@amd.com
Subject: Re: [PATCH v4 1/2] dt-bindings: arm: aspeed: Add AMD Onyx BMC compatible
Date: Tue, 18 Mar 2025 19:10:58 +0100 [thread overview]
Message-ID: <cebf6611-4a9f-48fa-9226-e4a559e75ab9@kernel.org> (raw)
In-Reply-To: <20250318174730.1921983-1-Rajaganesh.Rathinasabapathi@amd.com>
On 18/03/2025 18:47, 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(+)
Can you slow down and read submitting patches before posting or at least
get someone experienced in AMD to help you?
<form letter>
This is a friendly reminder during the review process.
It looks like you received a tag and forgot to add it.
If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions
of patchset, under or above your Signed-off-by tag, unless patch changed
significantly (e.g. new properties added to the DT bindings). Tag is
"received", when provided in a message replied to you on the mailing
list. Tools like b4 can help here. However, there's no need to repost
patches *only* to add the tags. The upstream maintainer will do that for
tags received on the version they apply.
Please read:
https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577
If a tag was not added on purpose, please state why and what changed.
</form letter>
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
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: conor+dt@kernel.org, linux-aspeed@lists.ozlabs.org,
linux-kernel@vger.kernel.org, jothayot@amd.com,
robh+dt@kernel.org, krzk+dt@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 1/2] dt-bindings: arm: aspeed: Add AMD Onyx BMC compatible
Date: Tue, 18 Mar 2025 19:10:58 +0100 [thread overview]
Message-ID: <cebf6611-4a9f-48fa-9226-e4a559e75ab9@kernel.org> (raw)
In-Reply-To: <20250318174730.1921983-1-Rajaganesh.Rathinasabapathi@amd.com>
On 18/03/2025 18:47, 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(+)
Can you slow down and read submitting patches before posting or at least
get someone experienced in AMD to help you?
<form letter>
This is a friendly reminder during the review process.
It looks like you received a tag and forgot to add it.
If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions
of patchset, under or above your Signed-off-by tag, unless patch changed
significantly (e.g. new properties added to the DT bindings). Tag is
"received", when provided in a message replied to you on the mailing
list. Tools like b4 can help here. However, there's no need to repost
patches *only* to add the tags. The upstream maintainer will do that for
tags received on the version they apply.
Please read:
https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577
If a tag was not added on purpose, please state why and what changed.
</form letter>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-18 18:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 17:47 [PATCH v4 1/2] dt-bindings: arm: aspeed: Add AMD Onyx BMC compatible Rajaganesh Rathinasabapathi
2025-03-18 17:47 ` Rajaganesh Rathinasabapathi
2025-03-18 17:47 ` [PATCH v4 2/2] ARM: dts: aspeed: Add Initial device tree for AMD Onyx Platform Rajaganesh Rathinasabapathi
2025-03-18 17:47 ` Rajaganesh Rathinasabapathi
2025-03-18 18:14 ` Krzysztof Kozlowski
2025-03-18 18:14 ` Krzysztof Kozlowski
2025-03-19 16:41 ` Rajaganesh Rathinasabapathi
2025-03-19 16:41 ` Rajaganesh Rathinasabapathi
2025-03-19 19:23 ` Krzysztof Kozlowski
2025-03-19 19:23 ` Krzysztof Kozlowski
2025-03-18 18:33 ` Andrew Lunn
2025-03-18 18:33 ` Andrew Lunn
2025-03-19 16:47 ` Rajaganesh Rathinasabapathi
2025-03-19 16:47 ` Rajaganesh Rathinasabapathi
2025-03-18 18:10 ` Krzysztof Kozlowski [this message]
2025-03-18 18:10 ` [PATCH v4 1/2] dt-bindings: arm: aspeed: Add AMD Onyx BMC compatible Krzysztof Kozlowski
2025-03-18 22:26 ` Rob Herring (Arm)
2025-03-18 22:26 ` Rob Herring (Arm)
2025-03-21 0:39 ` Andrew Jeffery
2025-03-21 0:39 ` 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=cebf6611-4a9f-48fa-9226-e4a559e75ab9@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=jothayot@amd.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.