From: Conor Dooley <conor@kernel.org>
To: Max Hsu <max.hsu@sifive.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Samuel Holland <samuel.holland@sifive.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Thomas Gleixner <tglx@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH 2/5] dt-bindings: interrupt-controller: Add SiFive FU740-C000 PLIC
Date: Fri, 20 Feb 2026 22:33:24 +0000 [thread overview]
Message-ID: <20260220-outdoors-shortwave-1d96b888d6c2@spud> (raw)
In-Reply-To: <CAHibDyy1mA2s9_UjKGPemRaKNSvyq07Ok5+4yruQ1uXX+R-Pkg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
On Sat, Feb 21, 2026 at 02:49:19AM +0800, Max Hsu wrote:
> On Fri, Feb 20, 2026 at 09:23:18 +0000, Conor Dooley wrote:
> > So do the general rules for devicetree bindings, that's not something
> > SiFive specific FWIW.
> > Acked-by: Conor Dooley <conor.dooley@microchip.com>
>
> Thanks for the review and the ack, Conor.
>
> I'll update the commit message in v2 to reference the general device
> tree conventions.
It's fine as-is, was just pointing out that this is a general guideline.
The SiFive document is mostly about the naming of the fallback
compatibles etc that represent the IP core, rather than the soc-specific
part.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-02-20 22:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 8:27 [PATCH 0/5] riscv: dts: sifive: fu740: Fix compatible strings per IP versioning Max Hsu
2026-02-20 8:27 ` [PATCH 1/5] dt-bindings: net: macb: Add SiFive FU740-C000 support Max Hsu
2026-02-20 9:29 ` Conor Dooley
2026-02-20 18:42 ` Max Hsu
2026-02-20 8:27 ` [PATCH 2/5] dt-bindings: interrupt-controller: Add SiFive FU740-C000 PLIC Max Hsu
2026-02-20 9:23 ` Conor Dooley
2026-02-20 18:49 ` Max Hsu
2026-02-20 22:33 ` Conor Dooley [this message]
2026-02-20 8:27 ` [PATCH 3/5] net: macb: Add support for SiFive FU740-C000 Max Hsu
2026-02-20 13:13 ` Andrew Lunn
2026-02-20 18:35 ` Max Hsu
2026-02-20 22:00 ` Conor Dooley
2026-02-20 8:27 ` [PATCH 4/5] riscv: dts: sifive: fu740: Use correct ethernet compatible string Max Hsu
2026-02-20 8:27 ` [PATCH 5/5] riscv: dts: sifive: fu740: Use correct PLIC " Max Hsu
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=20260220-outdoors-shortwave-1d96b888d6c2@spud \
--to=conor@kernel.org \
--cc=alex@ghiti.fr \
--cc=andrew+netdev@lunn.ch \
--cc=aou@eecs.berkeley.edu \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=max.hsu@sifive.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pabeni@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=tglx@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