From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Renze Nicolai <renze@rnplus.nl>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-aspeed@lists.ozlabs.org,
arnd@arndb.de, olof@lixom.net, soc@kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
joel@jms.id.au, andrew@aj.id.au
Subject: Re: [PATCH v2 1/2] dt-bindings: arm: aspeed: add Asrock X570D4U board
Date: Wed, 29 Nov 2023 09:23:06 +0100 [thread overview]
Message-ID: <9fcd5575-d127-4b25-99f0-e3a94e1e4477@linaro.org> (raw)
In-Reply-To: <20231128232456.2932350-2-renze@rnplus.nl>
On 29/11/2023 00:23, Renze Nicolai wrote:
> Document Asrock X570D4U compatible.
>
> Signed-off-by: Renze Nicolai <renze@rnplus.nl>
> ---
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, under or above your Signed-off-by tag. 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.
https://elixir.bootlin.com/linux/v6.5-rc3/source/Documentation/process/submitting-patches.rst#L577
If a tag was not added on purpose, please state why and what changed.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-11-29 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 23:23 [PATCH v2 0/2] ARM: dts: aspeed: asrock: Add ASRock X570D4U BMC Renze Nicolai
2023-11-28 23:23 ` [PATCH v2 1/2] dt-bindings: arm: aspeed: add Asrock X570D4U board Renze Nicolai
2023-11-29 8:23 ` Krzysztof Kozlowski [this message]
2023-11-28 23:23 ` [PATCH v2 2/2] ARM: dts: aspeed: asrock: Add ASRock X570D4U BMC Renze Nicolai
2023-12-01 2:09 ` Zev Weiss
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=9fcd5575-d127-4b25-99f0-e3a94e1e4477@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andrew@aj.id.au \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=renze@rnplus.nl \
--cc=robh+dt@kernel.org \
--cc=soc@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).