From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yixun Lan <dlan@gentoo.org>
Cc: michael.opdenacker@rootcommit.com, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, Yangyu Chen <cyy@cyyself.name>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: riscv: spacemit: Add OrangePi R2S board
Date: Tue, 11 Nov 2025 11:13:38 +0100 [thread overview]
Message-ID: <af7bd4ab-38dd-4a5a-93e5-f457ae3460db@kernel.org> (raw)
In-Reply-To: <20251111101149-GYE1651402@gentoo.org>
On 11/11/2025 11:11, Yixun Lan wrote:
> Hi Krzysztof,
>
> On 08:43 Tue 11 Nov , Krzysztof Kozlowski wrote:
>> On Mon, Nov 10, 2025 at 10:06:48PM +0000, michael.opdenacker@rootcommit.com wrote:
>>> From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
>>>
>>> Document the compatible string for the OrangePi R2S board [1], which
>>> is marketed as using the Ky X1 SoC but is in fact identical to
> Maybe, just say it "same" to clarify the ambiguity?
What is exactly "same"? Same die? Or same blocks/pieces? Whichever you
choose please make it very explicit.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-11 10:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251110220641.1751392-1-michael.opdenacker@rootcommit.com>
2025-11-10 22:06 ` [PATCH v3 1/2] dt-bindings: riscv: spacemit: Add OrangePi R2S board michael.opdenacker
2025-11-11 7:43 ` Krzysztof Kozlowski
2025-11-11 10:11 ` Yixun Lan
2025-11-11 10:13 ` Krzysztof Kozlowski [this message]
2025-11-11 10:29 ` Michael Opdenacker
2025-11-11 10:34 ` Krzysztof Kozlowski
2025-11-11 11:37 ` Michael Opdenacker
2025-11-11 11:41 ` Yixun Lan
2025-11-10 22:06 ` [PATCH v3 2/2] riscv: dts: spacemit: Add OrangePi R2S board device tree michael.opdenacker
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=af7bd4ab-38dd-4a5a-93e5-f457ae3460db@kernel.org \
--to=krzk@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=cyy@cyyself.name \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=michael.opdenacker@rootcommit.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
/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).