From: Linus Torvalds <torvalds@linux-foundation.org>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: Arnd Bergmann <arnd@arndb.de>, Eric Miao <eric.y.miao@gmail.com>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: mmp: replace NO_IRQ
Date: Tue, 6 Sep 2016 13:03:42 -0700 [thread overview]
Message-ID: <CA+55aFyrGTG3xzecScrTQKaqkZ96DizeH2aSjJENKB_DCD6hxA@mail.gmail.com> (raw)
In-Reply-To: <20160906194443.GC1041@n2100.armlinux.org.uk>
On Tue, Sep 6, 2016 at 12:44 PM, Russell King - ARM Linux
<linux@armlinux.org.uk> wrote:
>
> My point still stands though. Merely hiding it doesn't make the problem
> go away - it's just the same problem but now it won't be as visible, and
> as such it'll probably never get resolved.
How much of a legacy thing is this?
The main reason I'd like to _really_ make NO_IRQ go away is that it
seems that some people copy it from existing drivers, or just think
it's the RightThing(tm) to do because it looks so plausible.
So in that sense I wouldn't actually mind "merely hiding it".
It may not *fix* that particular driver or subsystem, but if it's
sufficiently well hidden or specialized, at least it won't cause the
pattern to be copied in the future, I'd hope.
So hiding things inside a particular driver (or a particular
subsystem) may be hacky from the standpoint of that particular driver
or subsystem, but from a "big issue" standpoint I don't mind at all.
Linus
next prev parent reply other threads:[~2016-09-06 20:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 14:07 [PATCH] ARM: mmp: replace NO_IRQ Arnd Bergmann
2016-09-06 14:24 ` Russell King - ARM Linux
2016-09-06 19:28 ` Arnd Bergmann
2016-09-06 19:44 ` Russell King - ARM Linux
2016-09-06 20:03 ` Linus Torvalds [this message]
2016-09-06 21:22 ` Russell King - ARM Linux
2016-09-08 20:16 ` Arnd Bergmann
2016-09-06 20:19 ` Arnd Bergmann
2016-09-06 20:41 ` Russell King - ARM Linux
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=CA+55aFyrGTG3xzecScrTQKaqkZ96DizeH2aSjJENKB_DCD6hxA@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=eric.y.miao@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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).