From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: David Woodhouse <dwmw2@infradead.org>,
Matthew Wilcox <matthew@wil.cx>,
Linux Arch list <linux-arch@vger.kernel.org>
Subject: Re: All archs: NO_IRQ definition
Date: Wed, 20 Oct 2004 18:24:37 +1000 [thread overview]
Message-ID: <1098260677.6263.1.camel@gaston> (raw)
In-Reply-To: <20041020091335.E1047@flint.arm.linux.org.uk>
On Wed, 2004-10-20 at 18:13, Russell King wrote:
> That's a bit of a problem - negative numbers means that an interrupt
> was detected, but that other interrupts also triggered... However,
> I don't think any driver actually makes use of this information.
Well, I hate that probe thing ... note that the current bk blows up
on me at boot with yenta_socket trying to do similar probing (hrm...
it should have a perfectly working PCI irq on ppc, and nothing else)
and the new "common" code actually implements that probe stuff... and
ends up calling a NULL function pointer. I'll have to check that out
too.
Anyway, I'll have a patch tonight or tomorrow after reviewing all
drivers using that interface. I'll also fix IDE & 8250 to use NO_IRQ,
I'll leave other drivers alone.
Ben.
next prev parent reply other threads:[~2004-10-20 8:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 6:57 All archs: NO_IRQ definition Benjamin Herrenschmidt
2004-10-19 9:22 ` Matthew Wilcox
2004-10-19 9:23 ` Russell King
2004-10-19 9:25 ` Matthew Wilcox
2004-10-19 9:27 ` David Woodhouse
2004-10-19 9:32 ` Geert Uytterhoeven
2004-10-20 3:26 ` Benjamin Herrenschmidt
2004-10-20 7:17 ` David Woodhouse
2004-10-20 8:13 ` Russell King
2004-10-20 8:24 ` Benjamin Herrenschmidt [this message]
2004-10-19 11:42 ` Ralf Baechle
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=1098260677.6263.1.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=dwmw2@infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=rmk@arm.linux.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 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.