[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ffeba9a68e72cf2cb97759c5fb496fac@kernel.org>
Date: Mon, 01 Jun 2020 08:41:00 +0100
From: Marc Zyngier <maz@...nel.org>
To: Anup Patel <anup@...infault.org>
Cc: Anup Patel <anup.patel@....com>,
Palmer Dabbelt <palmer@...belt.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Albert Ou <aou@...s.berkeley.edu>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Jason Cooper <jason@...edaemon.net>,
Atish Patra <atish.patra@....com>,
Alistair Francis <Alistair.Francis@....com>,
linux-riscv <linux-riscv@...ts.infradead.org>,
"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>,
Palmer Dabbelt <palmerdabbelt@...gle.com>
Subject: Re: [PATCH v6 3/6] irqchip: RISC-V per-HART local interrupt
controller driver
On 2020-06-01 05:09, Anup Patel wrote:
> On Sun, May 31, 2020 at 4:23 PM Marc Zyngier <maz@...nel.org> wrote:
>>
>> On 2020-05-31 11:06, Anup Patel wrote:
[...]
> Also, the PLIC spec is now owned by RISC-V foundation (not SiFive) so
> we will have to rename the driver to "irq-riscv-plic" and will have a
> new
> generic compatible string "riscv,plic-1.0.0". One of us (me or Palmer)
> will
> send separate patches for this renaming. I hope you will be fine with
> this??
> (Refer, https://github.com/riscv/riscv-plic-spec)
Do we really need the churn of a renaming? A new compatible, and maybe
a new config option should be enough, no? What does the renaming give
us?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
Powered by blists - more mailing lists