All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@kernel.org>
To: Anup Patel <anup@brainfault.org>
Cc: 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>
Subject: Re: Interrupt chip driver maintainence
Date: Sat, 05 Sep 2026 23:30:44 +0200	[thread overview]
Message-ID: <87ecf74c8r.ffs@fw13> (raw)
In-Reply-To: <CAAhSdy1=Z-VjEhGsGOJ15QptCSZP_6zG1NF=B972KwzEJhFbFg@mail.gmail.com>

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 think this is a fair ask.
>
> Currently, I am focused on reviewing and testing anything which
> touches RISC-V AIA drivers. The SiFive PLIC driver on other hand
> seems to have no active reivewers from RISC-V space. Few years
> back I did try to actively review SiFive PLIC driver but these days
> I don't have bandwidth for that.

I don't blame you and I put you on the CC list because you are in the
RISCV space.

I don't know what's wrong with SiFive but they really need to get their
act together. Paul?

Thanks,

        tglx

_______________________________________________
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: Thomas Gleixner <tglx@kernel.org>
To: Anup Patel <anup@brainfault.org>
Cc: 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>
Subject: Re: Interrupt chip driver maintainence
Date: Sat, 05 Sep 2026 23:30:44 +0200	[thread overview]
Message-ID: <87ecf74c8r.ffs@fw13> (raw)
In-Reply-To: <CAAhSdy1=Z-VjEhGsGOJ15QptCSZP_6zG1NF=B972KwzEJhFbFg@mail.gmail.com>

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 think this is a fair ask.
>
> Currently, I am focused on reviewing and testing anything which
> touches RISC-V AIA drivers. The SiFive PLIC driver on other hand
> seems to have no active reivewers from RISC-V space. Few years
> back I did try to actively review SiFive PLIC driver but these days
> I don't have bandwidth for that.

I don't blame you and I put you on the CC list because you are in the
RISCV space.

I don't know what's wrong with SiFive but they really need to get their
act together. Paul?

Thanks,

        tglx


  reply	other threads:[~2026-09-05 21:31 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
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 [this message]
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=87ecf74c8r.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=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 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.