From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
Andrew Morton <akpm@osdl.org>,
Andreas Mohr <andi@rhlx01.fht-esslingen.de>,
florin@iucha.net, linux-kernel@vger.kernel.org,
linux@dominikbrodowski.net
Subject: Re: pcmcia oops on 2.6.17-rc[12]
Date: Tue, 16 May 2006 00:00:26 +0100 [thread overview]
Message-ID: <1147734026.26686.200.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0605151459140.3866@g5.osdl.org>
On Llu, 2006-05-15 at 15:02 -0700, Linus Torvalds wrote:
> Note that some PCMCIA architectures simply _will_not_ give you a private
> IRQ. Ever. They may not have any ISA interrupts to give, even to old
> 16-bit cards. So the choice may be "shared irq or nothing".
Yes I realise that, the test patches in my tree will hand back a shared
one but hand back the status so you know you asked for exclusive, got
shared and need to decide.
> So I would strongly argue that any driver that depends on getting an
> exclusive IRQ is buggy, not the PCMCIA layer itself, and that it would be
> a lot more productive to try to fix those drivers.
It would certainly be a lot cleaner than this sort of code in the pcmcia
core right now. Want me to send a patch which only allows for SA_SHIRQ
and WARN_ON()'s for any driver not asking for shared IRQ ?
next prev parent reply other threads:[~2006-05-15 22:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-23 19:22 pcmcia oops on 2.6.17-rc[12] Florin Iucha
2006-04-23 22:02 ` Andrew Morton
2006-04-23 22:15 ` Randy.Dunlap
2006-04-24 0:46 ` Florin Iucha
2006-05-08 14:56 ` Andreas Mohr
2006-05-08 15:43 ` Andrew Morton
2006-05-08 16:34 ` Russell King
2006-05-15 22:07 ` Alan Cox
2006-05-15 22:00 ` Russell King
2006-05-18 11:10 ` Russell King
2006-05-15 22:02 ` Linus Torvalds
2006-05-15 23:00 ` Alan Cox [this message]
2006-05-15 23:37 ` Linus Torvalds
2006-05-15 23:52 ` Linus Torvalds
2006-05-16 0:17 ` Alan Cox
2006-05-16 0:18 ` Linus Torvalds
2006-05-16 1:18 ` Alan Cox
2006-05-16 15:16 ` Alan Cox
2006-05-22 11:50 ` Rogier Wolff
2006-05-22 12:10 ` Alan Cox
2006-05-22 21:27 ` Rogier Wolff
2006-05-22 22:38 ` Alan Cox
2006-06-02 19:09 ` Russell King
2006-05-22 15:06 ` Linus Torvalds
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=1147734026.26686.200.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=florin@iucha.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=torvalds@osdl.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.