From: Krzysztof Kozlowski <krzk@kernel.org>
To: Guo Ren <guoren@kernel.org>, robh@kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, robh+dt@kernel.org,
conor.dooley@microchip.com
Subject: Re: [PATCH 2/2] dt-bindings: riscv: Add Xuantie C906/C908/C910/C920 compatibles
Date: Mon, 17 Aug 2026 08:10:56 +0200 [thread overview]
Message-ID: <39a28db9-5ed3-427f-aae4-a08ee41c32c9@kernel.org> (raw)
In-Reply-To: <20260815015722.1736831-3-guoren@kernel.org>
On 15/08/2026 03:57, Guo Ren wrote:
> From: "GUO Ren (XuanTie)" <guoren@kernel.org>
>
> The RISC-V CPU bindings currently use the historical thead vendor
> prefix for the XuanTie C906, C908, C910 and C920 processors.
>
> Add equivalent compatibles using the newly defined xuantie vendor
> prefix. Keep the existing thead compatibles to preserve compatibility
> with existing device trees.
No, you already received feedback - you were on Cc, you replied, you got
answers.
https://lore.kernel.org/all/20251121-able-terrestrial-spaniel-90c3cf@kuoka/
NAK
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Guo Ren <guoren@kernel.org>, robh@kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, robh+dt@kernel.org,
conor.dooley@microchip.com
Subject: Re: [PATCH 2/2] dt-bindings: riscv: Add Xuantie C906/C908/C910/C920 compatibles
Date: Mon, 17 Aug 2026 08:10:56 +0200 [thread overview]
Message-ID: <39a28db9-5ed3-427f-aae4-a08ee41c32c9@kernel.org> (raw)
In-Reply-To: <20260815015722.1736831-3-guoren@kernel.org>
On 15/08/2026 03:57, Guo Ren wrote:
> From: "GUO Ren (XuanTie)" <guoren@kernel.org>
>
> The RISC-V CPU bindings currently use the historical thead vendor
> prefix for the XuanTie C906, C908, C910 and C920 processors.
>
> Add equivalent compatibles using the newly defined xuantie vendor
> prefix. Keep the existing thead compatibles to preserve compatibility
> with existing device trees.
No, you already received feedback - you were on Cc, you replied, you got
answers.
https://lore.kernel.org/all/20251121-able-terrestrial-spaniel-90c3cf@kuoka/
NAK
Best regards,
Krzysztof
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-08-17 6:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 1:57 [PATCH 0/2] dt-bindings: Add Xuantie Semiconductor Co., Ltd Guo Ren
2026-08-15 1:57 ` Guo Ren
2026-08-15 1:57 ` [PATCH 1/2] dt-bindings: vendor-prefixes: Add Xuantie Semiconductor Guo Ren
2026-08-15 1:57 ` Guo Ren
2026-08-17 6:08 ` Krzysztof Kozlowski
2026-08-17 6:08 ` Krzysztof Kozlowski
2026-08-17 9:42 ` Guo Ren
2026-08-17 9:42 ` Guo Ren
2026-08-15 1:57 ` [PATCH 2/2] dt-bindings: riscv: Add Xuantie C906/C908/C910/C920 compatibles Guo Ren
2026-08-15 1:57 ` Guo Ren
2026-08-15 2:02 ` sashiko-bot
2026-08-15 19:44 ` Shengyu Qu
2026-08-15 19:44 ` Shengyu Qu
2026-08-17 1:40 ` Guo Ren
2026-08-17 1:40 ` Guo Ren
2026-08-17 6:10 ` Krzysztof Kozlowski [this message]
2026-08-17 6:10 ` Krzysztof Kozlowski
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=39a28db9-5ed3-427f-aae4-a08ee41c32c9@kernel.org \
--to=krzk@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=guoren@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=robh+dt@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.