From: Conor Dooley <conor@kernel.org>
To: Lucas Zampieri <lzampier@redhat.com>
Cc: devicetree@vger.kernel.org,
Charles Mirabile <cmirabil@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Samuel Holland <samuel.holland@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Vivian Wang <dramforever@live.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] dt-bindings: interrupt-controller: add UltraRISC DP1000 PLIC
Date: Mon, 13 Oct 2025 19:25:54 +0100 [thread overview]
Message-ID: <20251013-commute-bountiful-208ade035c86@spud> (raw)
In-Reply-To: <20251013111539.2206477-3-lzampier@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]
On Mon, Oct 13, 2025 at 12:15:37PM +0100, Lucas Zampieri wrote:
> From: Charles Mirabile <cmirabil@redhat.com>
>
> Add a new compatible string for UltraRISC DP1000 PLIC.
>
> Signed-off-by: Charles Mirabile <cmirabil@redhat.com>
> Signed-off-by: Lucas Zampieri <lzampier@redhat.com>
> ---
> .../bindings/interrupt-controller/sifive,plic-1.0.0.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml b/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml
> index 5b827bc24301..a419de50f5a8 100644
> --- a/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml
> +++ b/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml
> @@ -74,6 +74,8 @@ properties:
> - sophgo,sg2044-plic
> - thead,th1520-plic
> - const: thead,c900-plic
> + - items:
> + - const: ultrarisc,dp1000-plic
> + - const: ultrarisc,cp100-plic
Based on your cover letter, this is problem not incorrect, but this fails
the eye test and looks wrong. Please mention in your commit message that
dp1000 is an soc and cp100 is a purchasable IP core.
pw-bot: changes-requested
> - items:
> - const: sifive,plic-1.0.0
> - const: riscv,plic0
> --
> 2.51.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-10-13 18:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 11:15 [PATCH v2 0/3] Add UltraRISC DP1000 PLIC support Lucas Zampieri
2025-10-13 11:15 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: add UltraRISC Lucas Zampieri
2025-10-13 11:15 ` [PATCH v2 2/3] dt-bindings: interrupt-controller: add UltraRISC DP1000 PLIC Lucas Zampieri
2025-10-13 18:25 ` Conor Dooley [this message]
2025-10-13 11:15 ` [PATCH v2 3/3] irqchip/plic: add support for " Lucas Zampieri
2025-10-13 18:30 ` Conor Dooley
2025-10-14 9:14 ` Vivian Wang
2025-10-14 14:35 ` Lucas Zampieri
2025-10-14 17:47 ` Conor Dooley
2025-10-13 19:00 ` Samuel Holland
2025-10-13 21:03 ` Charles Mirabile
2025-10-13 21:58 ` Samuel Holland
2025-10-13 21:24 ` Bo Gan
2025-10-13 22:04 ` Samuel Holland
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=20251013-commute-bountiful-208ade035c86@spud \
--to=conor@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=cmirabil@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dramforever@live.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lzampier@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=tglx@linutronix.de \
/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