From: Krzysztof Kozlowski <krzk@kernel.org>
To: Peter Chen <peter.chen@cixtech.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
catalin.marinas@arm.com, will@kernel.org, arnd@arndb.de
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, cix-kernel-upstream@cixtech.com,
marcin@juszkiewicz.com.pl, Fugang Duan <fugang.duan@cixtech.com>
Subject: Re: [PATCH v2 2/6] dt-bindings: arm: add CIX P1 (SKY1) SoC
Date: Wed, 26 Feb 2025 08:02:12 +0100 [thread overview]
Message-ID: <f89817fe-22af-460e-9f5c-a3347eba1892@kernel.org> (raw)
In-Reply-To: <20250226012136.854614-3-peter.chen@cixtech.com>
On 26/02/2025 02:21, Peter Chen wrote:
> Add device tree bindings for CIX P1 (Internal name sky1) Arm SoC,
> it consists several SoC models like CP8180, CD8180, etc.
>
> Acked-by: Fugang Duan <fugang.duan@cixtech.com>
> Signed-off-by: Peter Chen <peter.chen@cixtech.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-02-26 7:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 1:21 [PATCH v2 0/6] arm64: Introduce CIX P1 (SKY1) SoC Peter Chen
2025-02-26 1:21 ` [PATCH v2 1/6] dt-bindings: vendor-prefixes: Add CIX Technology Group Co., Ltd Peter Chen
2025-02-26 7:02 ` Krzysztof Kozlowski
2025-02-26 10:31 ` Krzysztof Kozlowski
2025-02-26 1:21 ` [PATCH v2 2/6] dt-bindings: arm: add CIX P1 (SKY1) SoC Peter Chen
2025-02-26 7:02 ` Krzysztof Kozlowski [this message]
2025-02-26 8:09 ` Peter Chen
2025-02-26 8:40 ` Krzysztof Kozlowski
2025-02-26 10:26 ` Peter Chen
2025-02-26 10:30 ` Krzysztof Kozlowski
2025-02-26 12:59 ` Peter Chen
2025-02-26 1:21 ` [PATCH v2 3/6] MAINTAINERS: Add CIX SoC maintainer entry Peter Chen
2025-02-26 1:21 ` [PATCH v2 4/6] arm64: Kconfig: add ARCH_CIX for cix silicons Peter Chen
2025-02-26 1:21 ` [PATCH v2 5/6] arm64: defconfig: Enable CIX SoC Peter Chen
2025-02-26 1:21 ` [PATCH v2 6/6] arm64: dts: cix: add initial CIX P1(SKY1) dts support Peter Chen
2025-02-26 7:05 ` Krzysztof Kozlowski
2025-02-27 4:52 ` [PATCH v2 0/6] arm64: Introduce CIX P1 (SKY1) SoC Jianfeng Liu
2025-02-27 8:02 ` Peter Chen
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=f89817fe-22af-460e-9f5c-a3347eba1892@kernel.org \
--to=krzk@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fugang.duan@cixtech.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin@juszkiewicz.com.pl \
--cc=peter.chen@cixtech.com \
--cc=robh@kernel.org \
--cc=will@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).