Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@kernel.org>
To: Nam Cao <namcao@linutronix.de>, LKML <linux-kernel@vger.kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-riscv@lists.infradead.org, Radu Rendec <radu@rendec.net>,
	Marc Zyngier <maz@kernel.org>, Anup Patel <anup@brainfault.org>,
	Paul Walmsley <pjw@kernel.org>
Subject: Re: Interrupt chip driver maintainence
Date: Sat, 05 Sep 2026 21:12:30 +0200	[thread overview]
Message-ID: <87fqzn5x7l.ffs@fw13> (raw)
In-Reply-To: <87ld9g9zrt.fsf@yellow.woof>

Nam!

On Sat, Sep 05 2026 at 04:51, Nam Cao wrote:
> Thomas Gleixner <tglx@kernel.org> writes:
>> I'm wading through my inbox full of patches for interrupt chip drivers
>> and I'm thoroughly annoyed. The way how this works today is not
>> sustainable.
>>
>> Patches end up in my and Radu's inbox and all we can do is go through
>> them mostly on a formal basis, but it's out of our scope to look at the
>> correctness vs. a particular hardware. In the past I just picked up
>> patches when I had the gut feeling they are remotely correct, but I'm
>> tired of this.
>
> I have hardware to test the SiFive PLIC. I also spent quite some time
> staring at the specification attempting to cleanse the mess we have for
> plic_irq_eoi() (which sadly yielded nothing).
>
> I can help looking at patches. Would that help moving things forward?

Help is always welcome.

But the point is that the companies who build and sell that stuff have
the responsibility to take care of it and not just dump their crap into
the kernel and then expect that someone else will take care of it for
free.

If SiFive pays you or your employer to provide that service that's fine,
but you doing it on your on [dt]ime to proliferate the carelessness of
those who profit from it is just wrong.

Thanks,

        tglx

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2026-09-05 19:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 14:49 Interrupt chip driver maintainence 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 [this message]
2026-09-05 11:07 ` Anup Patel
2026-09-05 21:30   ` Thomas Gleixner

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=87fqzn5x7l.ffs@fw13 \
    --to=tglx@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=namcao@linutronix.de \
    --cc=pjw@kernel.org \
    --cc=radu@rendec.net \
    /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