From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jason Hsu <jasonhell19@gmail.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
joel@jms.id.au, andrew@codeconstruct.com.au, patrick@stwcx.xyz,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: yang.chen@quantatw.com, jerry.lin@quantatw.com
Subject: Re: [PATCH v7 1/2] ARM: dts: aspeed: ventura: add Meta Ventura BMC
Date: Fri, 6 Jun 2025 08:50:47 +0200 [thread overview]
Message-ID: <44b72ea6-353f-40bd-9bbc-66186bdb1161@kernel.org> (raw)
In-Reply-To: <20250606025251.887953-2-jasonhell19@gmail.com>
On 06/06/2025 04:52, Jason Hsu wrote:
> Add Linux device tree related to Meta(Facebook) Ventura specific
> devices connected to BMC(AST2600) SoC.Add subject prefix for the patch.
>
> Signed-off-by: Jason Hsu <jasonhell19@gmail.com>
<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-06-06 7:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 2:52 [PATCH v7 0/2] Add Meta(Facebook) Ventura BMC(AST2600) Jason Hsu
2025-06-06 2:52 ` [PATCH v7 1/2] ARM: dts: aspeed: ventura: add Meta Ventura BMC Jason Hsu
2025-06-06 6:50 ` Krzysztof Kozlowski [this message]
2025-06-06 2:52 ` [PATCH v7 2/2] dt-bindings: arm: aspeed: add Meta Ventura board Jason Hsu
2025-06-06 6:52 ` Krzysztof Kozlowski
2025-06-11 12:16 ` 徐傑生
2025-06-06 13:14 ` [PATCH v7 0/2] Add Meta(Facebook) Ventura BMC(AST2600) Rob Herring (Arm)
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=44b72ea6-353f-40bd-9bbc-66186bdb1161@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jasonhell19@gmail.com \
--cc=jerry.lin@quantatw.com \
--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=patrick@stwcx.xyz \
--cc=robh@kernel.org \
--cc=yang.chen@quantatw.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).