All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nam Cao <namcao@linutronix.de>
To: Thomas Gleixner <tglx@kernel.org>, 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 04:51:18 +0200	[thread overview]
Message-ID: <87ld9g9zrt.fsf@yellow.woof> (raw)
In-Reply-To: <871pb9841j.ffs@fw13>

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?

Nam

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

WARNING: multiple messages have this Message-ID (diff)
From: Nam Cao <namcao@linutronix.de>
To: Thomas Gleixner <tglx@kernel.org>, 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 04:51:18 +0200	[thread overview]
Message-ID: <87ld9g9zrt.fsf@yellow.woof> (raw)
In-Reply-To: <871pb9841j.ffs@fw13>

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?

Nam


  parent reply	other threads:[~2026-09-05  2:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 14:49 Interrupt chip driver maintainence Thomas Gleixner
2026-09-04 14:49 ` Thomas Gleixner
2026-09-04 15:01 ` Marc Zyngier
2026-09-04 15:01   ` Marc Zyngier
2026-09-05  0:46 ` Radu Rendec
2026-09-05  0:46   ` Radu Rendec
2026-09-05  2:51 ` Nam Cao [this message]
2026-09-05  2:51   ` Nam Cao
2026-09-05 19:12   ` Thomas Gleixner
2026-09-05 19:12     ` Thomas Gleixner
2026-09-05 11:07 ` Anup Patel
2026-09-05 11:07   ` Anup Patel
2026-09-05 21:30   ` Thomas Gleixner
2026-09-05 21:30     ` Thomas Gleixner
2026-09-11 18:07     ` Paul Walmsley
2026-09-11 18:07       ` Paul Walmsley

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=87ld9g9zrt.fsf@yellow.woof \
    --to=namcao@linutronix.de \
    --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=pjw@kernel.org \
    --cc=radu@rendec.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.