From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: ksummit-discuss@lists.linuxfoundation.org, "Nikula,
Jani" <jani.nikula@linux.intel.com>,
Dave Airlie <airlied@linux.ie>,
Grant Likely <grant.likely@linaro.org>,
ppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] (group) maintainership models
Date: Sat, 03 Sep 2016 08:16:51 +1000 [thread overview]
Message-ID: <1472854611.2313.5.camel@kernel.crashing.org> (raw)
In-Reply-To: <CA+55aFzw-KkQOhVJG+c-WEFA=6o5aXy=yU9KXQ7jwy-xy--d9Q@mail.gmail.com>
On Fri, 2016-09-02 at 13:26 -0700, Linus Torvalds wrote:
> On Fri, Sep 2, 2016 at 1:06 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> >
> >
> > When I once looked, I thought all drivers using NO_IRQ were
> > specific
> > to powerpc or one of the less common architectures.
We deprecated NO_IRQ ages ago, it's 0 like it should be, but yes we may
have forgotten to "cleanup" the old users.
> powerpc definitely does seem to be the biggest case, with about half
> the instances of NO_IRQ being under arch/powerpc/ (and a few more in
> ppc-specific drivers).
>
> Adding the powerpc maintainers to the list - because it would really
> be nice to get rid of it, or at least make it *so* rare that we don't
> have people re-introducing it again because they thought it was the
> right thing to do.
Right. Originally it was -1 for us which causes the whole problem. I
changed it to be 0 after doing the whole irq domain remapping thing.
That was a loooong time ago.
> A fair amount of of it could even be done by some trivial scripting.
> Something like
>
> git grep -wl NO_IRQ arch/powerpc/ | while read a
> do
> sed 's/(\([a-z_]*irq\) != NO_IRQ)/(\1)/' < $a > $a.new
> sed 's/(\([a-z_]*irq\) == NO_IRQ)/(!\1)/' < $a.new > $a
> done
>
> does fix at least a few of the cases. It still leaves several
> assignments and "return NO_IRQ;" statements, but a few more
> sed-scripts would take care of most of it. Then remove the #define,
> and do a full build to find any straggling cases.
>
> Michael? Ben?
It can just be replaced with "0" in all powerpc related cases yes.
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: Vinod Koul <vinod.koul@intel.com>,
Mark Brown <broonie@kernel.org>,
ksummit-discuss@lists.linuxfoundation.org,
Dave Airlie <airlied@linux.ie>,
"Nikula, Jani" <jani.nikula@linux.intel.com>,
Grant Likely <grant.likely@linaro.org>,
ppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] (group) maintainership models
Date: Sat, 03 Sep 2016 08:16:51 +1000 [thread overview]
Message-ID: <1472854611.2313.5.camel@kernel.crashing.org> (raw)
In-Reply-To: <CA+55aFzw-KkQOhVJG+c-WEFA=6o5aXy=yU9KXQ7jwy-xy--d9Q@mail.gmail.com>
On Fri, 2016-09-02 at 13:26 -0700, Linus Torvalds wrote:
> On Fri, Sep 2, 2016 at 1:06 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> >
> >
> > When I once looked, I thought all drivers using NO_IRQ were
> > specific
> > to powerpc or one of the less common architectures.
We deprecated NO_IRQ ages ago, it's 0 like it should be, but yes we may
have forgotten to "cleanup" the old users.
> powerpc definitely does seem to be the biggest case, with about half
> the instances of NO_IRQ being under arch/powerpc/ (and a few more in
> ppc-specific drivers).
>
> Adding the powerpc maintainers to the list - because it would really
> be nice to get rid of it, or at least make it *so* rare that we don't
> have people re-introducing it again because they thought it was the
> right thing to do.
Right. Originally it was -1 for us which causes the whole problem. I
changed it to be 0 after doing the whole irq domain remapping thing.
That was a loooong time ago.
> A fair amount of of it could even be done by some trivial scripting.
> Something like
>
> git grep -wl NO_IRQ arch/powerpc/ | while read a
> do
> sed 's/(\([a-z_]*irq\) != NO_IRQ)/(\1)/' < $a > $a.new
> sed 's/(\([a-z_]*irq\) == NO_IRQ)/(!\1)/' < $a.new > $a
> done
>
> does fix at least a few of the cases. It still leaves several
> assignments and "return NO_IRQ;" statements, but a few more
> sed-scripts would take care of most of it. Then remove the #define,
> and do a full build to find any straggling cases.
>
> Michael? Ben?
It can just be replaced with "0" in all powerpc related cases yes.
Cheers,
Ben.
next prev parent reply other threads:[~2016-09-02 22:34 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 12:11 [Ksummit-discuss] [CORE TOPIC] (group) maintainership models Daniel Vetter
2016-07-22 20:02 ` Darren Hart
2016-07-25 5:57 ` Daniel Vetter
2016-07-26 16:22 ` Darren Hart
2016-07-28 22:13 ` Bjorn Helgaas
2016-07-26 16:45 ` Olof Johansson
2016-07-27 3:04 ` Vinod Koul
2016-07-27 5:34 ` Wolfram Sang
2016-07-27 7:53 ` Arnd Bergmann
2016-07-27 12:57 ` Vinod Koul
2016-07-27 14:22 ` Mark Brown
2016-07-27 17:15 ` Vinod Koul
2016-07-28 8:44 ` Arnd Bergmann
2016-07-28 23:48 ` Alexandre Belloni
2016-07-29 0:06 ` Stephen Rothwell
2016-07-31 17:57 ` Vinod Koul
2016-08-01 6:56 ` Arnd Bergmann
2016-08-01 7:36 ` Laurent Pinchart
2016-08-01 14:10 ` Arnd Bergmann
2016-08-02 4:46 ` Vinod Koul
2016-08-02 6:48 ` Peter Ujfalusi
2016-08-02 7:27 ` Arnd Bergmann
2016-08-02 8:29 ` Peter Ujfalusi
2016-08-02 8:33 ` Laurent Pinchart
2016-08-02 9:49 ` Tony Lindgren
2016-08-02 8:41 ` Russell King - ARM Linux
2016-08-02 9:21 ` Laurent Pinchart
2016-08-02 9:27 ` Russell King - ARM Linux
2016-09-02 10:46 ` Vinod Koul
2016-09-02 17:25 ` Linus Torvalds
2016-09-02 20:06 ` Arnd Bergmann
2016-09-02 20:26 ` Linus Torvalds
2016-09-02 20:26 ` Linus Torvalds
2016-09-02 20:43 ` Julia Lawall
2016-09-02 20:43 ` Julia Lawall
2016-09-02 20:50 ` Linus Torvalds
2016-09-02 20:50 ` Linus Torvalds
2016-09-02 22:16 ` Benjamin Herrenschmidt [this message]
2016-09-02 22:16 ` Benjamin Herrenschmidt
2016-09-03 14:02 ` Michael Ellerman
2016-09-03 14:02 ` Michael Ellerman
2016-09-02 23:35 ` Arnd Bergmann
2016-09-04 17:45 ` Geert Uytterhoeven
2016-09-04 17:59 ` Linus Torvalds
2016-09-03 0:07 ` Mark Brown
2016-07-27 12:59 ` Daniel Vetter
2016-07-27 13:03 ` Daniel Vetter
2016-08-01 14:42 ` Jani Nikula
-- strict thread matches above, loose matches on Subject: below --
2016-09-07 5:03 Leon Romanovsky
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=1472854611.2313.5.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=airlied@linux.ie \
--cc=arnd@arndb.de \
--cc=grant.likely@linaro.org \
--cc=jani.nikula@linux.intel.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=torvalds@linux-foundation.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.