From: Krzysztof Kozlowski <krzk@kernel.org>
To: wjjsn <wjjsn@qq.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
chenhuacai@kernel.org
Cc: kernel@xen0n.name, devicetree@vger.kernel.org,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] loongarch: boot: dts: Add Loongson-2K0300 support
Date: Sun, 22 Mar 2026 09:53:39 +0100 [thread overview]
Message-ID: <58a4ee0d-5473-469c-9cce-a6888353c846@kernel.org> (raw)
In-Reply-To: <tencent_6034EC6B5DDA04A0956AEDECE445442AE406@qq.com>
On 22/03/2026 07:02, wjjsn wrote:
> Signed-off-by: wjjsn <wjjsn@qq.com>
> ---
> .../bindings/loongarch/loongson.yaml | 2 +-
> arch/loongarch/boot/dts/Makefile | 2 +-
> .../boot/dts/loongson-2k0300-ref.dts | 34 +++++++
> arch/loongarch/boot/dts/loongson-2k0300.dtsi | 95 +++++++++++++++++++
Random posting.
> 4 files changed, 131 insertions(+), 2 deletions(-)
> create mode 100644 arch/loongarch/boot/dts/loongson-2k0300-ref.dts
> create mode 100644 arch/loongarch/boot/dts/loongson-2k0300.dtsi
>
> diff --git a/Documentation/devicetree/bindings/loongarch/loongson.yaml b/Documentation/devicetree/bindings/loongarch/loongson.yaml
> index 8bea8b9f75b1..8e0a917ffc01 100644
> --- a/Documentation/devicetree/bindings/loongarch/loongson.yaml
> +++ b/Documentation/devicetree/bindings/loongarch/loongson.yaml
> @@ -16,7 +16,7 @@ properties:
> oneOf:
> - description: Loongson-2K0300 processor based boards
> items:
> - - const: loongson,99pi
But this is obviously NAK without explanation.
> + - const: loongson,ls2k0300-ref
Best regards,
Krzysztof
prev parent reply other threads:[~2026-03-22 8:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260322060246.1375569-1-wjjsn@qq.com>
2026-03-22 6:02 ` [PATCH v3 1/2] dt-bindings: loongarch: Add Loongson-2K0300 wjjsn
2026-03-22 6:02 ` [PATCH v3 2/2] loongarch: boot: dts: Add Loongson-2K0300 support wjjsn
2026-03-22 8:53 ` Krzysztof Kozlowski [this message]
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=58a4ee0d-5473-469c-9cce-a6888353c846@kernel.org \
--to=krzk@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@xen0n.name \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=robh@kernel.org \
--cc=wjjsn@qq.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 read-only IMAP folder(s) and NNTP newsgroup(s).