From: Krzysztof Kozlowski <krzk@kernel.org>
To: FUKAUMI Naoki <naoki@radxa.com>, Joseph Kogut <joseph.kogut@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org,
Steve deRosier <derosier@cal-sierra.com>
Subject: Re: [PATCH v3 1/3] dt-bindings: arm: rockchip: Add Radxa CM5 IO board
Date: Tue, 28 Oct 2025 11:42:21 +0100 [thread overview]
Message-ID: <400d08a1-c373-4efa-8ec4-f535e74acd98@kernel.org> (raw)
In-Reply-To: <2f4e7f94-2921-493c-94fa-45749a060bc0@kernel.org>
On 28/10/2025 10:37, Krzysztof Kozlowski wrote:
> On 28/10/2025 10:33, FUKAUMI Naoki wrote:
>> Hi Krzysztof,
>>
>> https://patchwork.kernel.org/project/linux-rockchip/patch/20250528221823.2974653-2-joseph.kogut@gmail.com/
>>
>> On 5/29/25 18:19, Krzysztof Kozlowski wrote:
>>> On Wed, May 28, 2025 at 03:18:21PM GMT, Joseph Kogut wrote:
>>>> Add device tree binding for the Radxa CM5 IO board.
>>>>
>>>> This board is based on the rk3588s.
>>>
>>> Do not attach (thread) your patchsets to some other threads (unrelated
>>> or older versions). This buries them deep in the mailbox and might
>>> interfere with applying entire sets.
>>>
>>>
>>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> Please explain the sorting rule used for this file. You must have known
>> the sorting rule; otherwise, how can you be sure this patch is correct?
>
> Huh? I don't have a clue about sorting rule but if you mock my review
> let's make it different:
>
> NAK
Please ignore, I thought that's patch from FUKAUMI Naoki which code and
then pokes about that.
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:[~2025-10-28 10:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 22:00 [PATCH v2 1/2] dt-bindings: arm: rockchip: Add Radxa CM5 IO board Joseph Kogut
2025-05-15 22:00 ` [PATCH v2 2/2] arm64: dts: rockchip: add Radxa CM5 and " Joseph Kogut
2025-05-15 23:22 ` [PATCH v2 1/2] dt-bindings: arm: rockchip: Add Radxa CM5 " Rob Herring (Arm)
2025-05-28 22:18 ` [PATCH v3 0/3] Add Radxa CM5 module and IO board dts Joseph Kogut
2025-05-28 22:18 ` [PATCH v3 1/3] dt-bindings: arm: rockchip: Add Radxa CM5 IO board Joseph Kogut
2025-05-29 9:19 ` Krzysztof Kozlowski
2025-05-29 17:00 ` Joseph Kogut
2025-05-29 17:07 ` Krzysztof Kozlowski
2025-05-29 17:26 ` Joseph Kogut
2025-10-28 9:33 ` FUKAUMI Naoki
2025-10-28 9:37 ` Krzysztof Kozlowski
2025-10-28 9:44 ` FUKAUMI Naoki
2025-10-28 10:41 ` Krzysztof Kozlowski
2025-11-05 1:37 ` FUKAUMI Naoki
2025-11-05 6:42 ` Krzysztof Kozlowski
2025-11-14 8:18 ` FUKAUMI Naoki
2025-10-28 10:42 ` Krzysztof Kozlowski [this message]
2025-05-28 22:18 ` [PATCH v3 2/3] arm64: dts: rockchip: Add rk3588 based Radxa CM5 Joseph Kogut
2025-05-28 22:18 ` [PATCH v3 3/3] arm64: dts: rockchip: Add support for CM5 IO carrier Joseph Kogut
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=400d08a1-c373-4efa-8ec4-f535e74acd98@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=derosier@cal-sierra.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=joseph.kogut@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=naoki@radxa.com \
--cc=robh@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