From: Marc Zyngier <maz@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Peng Fan <peng.fan@nxp.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"brgl@bgdev.pl" <brgl@bgdev.pl>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: GPIO TODO
Date: Tue, 18 Mar 2025 10:18:45 +0000 [thread overview]
Message-ID: <86v7s6myka.wl-maz@kernel.org> (raw)
In-Reply-To: <CACRpkdbHr_CpoqGwE+mXxV0My30ZcBRJmK9313fXN0rbPDPbDA@mail.gmail.com>
On Tue, 18 Mar 2025 10:00:16 +0000,
Linus Walleij <linus.walleij@linaro.org> wrote:
>
> On Tue, Mar 18, 2025 at 8:38 AM Peng Fan <peng.fan@nxp.com> wrote:
>
> > Besides the of_gpio.h, anyone working on immutable
> > irq_chip?
>
> This work was initiated by Marc Zyngier and he has since had
> to resign irqchip maintenance so it lands with Tomas Gleixner that
> has too much to do (I think), but rest assured that he will be
> grateful if you pick it up, so just send patches.
You of course still have the option to simply delete anything that is
not yet immutable, or remove the irq_chip patching support. The kernel
has been screaming for three years now, and these drivers are pretty
much unmaintained.
My bet is that nobody will notice, and I suspect tglx will gladly take
patches deleting unmaintained code. Once that's done, you can drop the
immutable flag, which won't serve any purpose anymore.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-03-18 10:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 7:37 GPIO TODO Peng Fan
2025-03-18 9:22 ` Andy Shevchenko
2025-03-18 9:58 ` Peng Fan
2025-03-18 10:10 ` Andy Shevchenko
2025-03-18 10:00 ` Linus Walleij
2025-03-18 10:18 ` Marc Zyngier [this message]
2025-03-18 14:51 ` Peng Fan
2025-03-18 15:09 ` Marc Zyngier
2025-03-20 14:30 ` Linus Walleij
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=86v7s6myka.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=peng.fan@nxp.com \
/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;
as well as URLs for NNTP newsgroup(s).