From: Paul Walmsley <pjw@kernel.org>
To: Thomas Gleixner <tglx@kernel.org>
Cc: Anup Patel <anup@brainfault.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org, Radu Rendec <radu@rendec.net>,
Marc Zyngier <maz@kernel.org>, Paul Walmsley <pjw@kernel.org>,
samuel.holland@sifive.com
Subject: Re: Interrupt chip driver maintainence
Date: Fri, 11 Sep 2026 12:07:31 -0600 (MDT) [thread overview]
Message-ID: <295ecaaa-fca0-05c2-ddaf-ad3a2985776d@kernel.org> (raw)
In-Reply-To: <87ecf74c8r.ffs@fw13>
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
+ Samuel
Hi Thomas,
Sorry for the delay; I've been on vacation this week.
On Sat, 5 Sep 2026, Thomas Gleixner wrote:
> On Sat, Sep 05 2026 at 16:37, Anup Patel wrote:
> > On Fri, Sep 4, 2026 at 8:19 PM Thomas Gleixner <tglx@kernel.org> wrote:
> >> I'm still going to pick up obvious and simple bug fixes, but for
> >> anything which requires deep knowledge on the underlying hardware, I'm
> >> going to just mark them obsolete when they molded in my inbox unreviewed
> >> by the people who understand it for six weeks.
>
[ ... ]
>
> I don't know what's wrong with SiFive but they really need to get their
> act together. Paul?
The approach you described above is fine. Please feel free to ignore
anything beyond bug fixes that doesn't have an appropriate ack, at least
until we figure out how to broaden the pool of maintainers for those
drivers.
For what it's worth, several other companies also adopted SiFive PLIC-like
interrupt controllers, and reuse those drivers. It would be great if
kernel folks from those other companies can step in and help maintain the
underlying code.
thanks,
- Paul
prev parent reply other threads:[~2026-09-11 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 14:49 Thomas Gleixner
2026-09-04 15:01 ` Marc Zyngier
2026-09-05 0:46 ` Radu Rendec
2026-09-05 2:51 ` Nam Cao
2026-09-05 19:12 ` Thomas Gleixner
2026-09-05 11:07 ` Anup Patel
2026-09-05 21:30 ` Thomas Gleixner
2026-09-11 18:07 ` Paul Walmsley [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=295ecaaa-fca0-05c2-ddaf-ad3a2985776d@kernel.org \
--to=pjw@kernel.org \
--cc=anup@brainfault.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.org \
--cc=radu@rendec.net \
--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
all inboxes | Powered by JetHome®