From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Nicolas Frattaroli <frattaroli.nicolas@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/4] dt-bindings: arm: rockchip: Add SOQuartz Blade
Date: Wed, 16 Nov 2022 13:47:21 +0100 [thread overview]
Message-ID: <e34d73e8-9adb-beea-ec88-5d440012db5b@linaro.org> (raw)
In-Reply-To: <20221116115337.541601-2-frattaroli.nicolas@gmail.com>
On 16/11/2022 12:53, Nicolas Frattaroli wrote:
> This adds an enum for the SOQuartz Blade base board to the rockchip
Do not use "This commit/patch".
https://elixir.bootlin.com/linux/v5.17.1/source/Documentation/process/submitting-patches.rst#L95
> platforms binding.
You do not add enum. You add compatible for the or document the SOQuartz
Blade.
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2022-11-16 12:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 11:53 [PATCH v3 0/4] Misc SOQuartz Enablement Nicolas Frattaroli
2022-11-16 11:53 ` [PATCH v3 1/4] dt-bindings: arm: rockchip: Add SOQuartz Blade Nicolas Frattaroli
2022-11-16 12:47 ` Krzysztof Kozlowski [this message]
2022-11-16 11:53 ` [PATCH v3 2/4] arm64: dts: rockchip: Add SOQuartz blade board Nicolas Frattaroli
2022-11-16 11:53 ` [PATCH v3 3/4] dt-bindings: arm: rockchip: Add SOQuartz Model A Nicolas Frattaroli
2022-11-16 12:47 ` Krzysztof Kozlowski
2022-11-16 11:53 ` [PATCH v3 4/4] arm64: dts: rockchip: rk3566: Add SOQuartz Model A baseboard Nicolas Frattaroli
2022-11-22 22:34 ` [PATCH v3 0/4] Misc SOQuartz Enablement Heiko Stuebner
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=e34d73e8-9adb-beea-ec88-5d440012db5b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=frattaroli.nicolas@gmail.com \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox