From: Matthew Wilcox <matthew@wil.cx>
To: Frederik Deweerdt <deweerdt@free.fr>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-kernel@vger.kernel.org, arjan@infradead.org,
alan@lxorguk.ukuu.org.uk, akpm@osdl.org, rdunlap@xenotime.net,
gregkh@suse.de
Subject: Re: [RFC PATCH] add pci_{request,free}_irq take #3
Date: Wed, 4 Oct 2006 14:33:11 -0600 [thread overview]
Message-ID: <20061004203311.GI28596@parisc-linux.org> (raw)
In-Reply-To: <20061004202938.GF352@slug>
On Wed, Oct 04, 2006 at 08:29:38PM +0000, Frederik Deweerdt wrote:
> I see. Just to be sure that I got the matter right, does the issue boils
> down to a choice between:
woah, woah, woah, you're getting yourself confused here.
You're looking at what the architectures do here. We're not concerned
with that, we're concerned with what the device drivers do with whatever
value the architecture has stuck in pdev->irq.
next prev parent reply other threads:[~2006-10-04 20:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 19:32 [RFC PATCH] add pci_{request,free}_irq take #3 Frederik Deweerdt
2006-10-04 19:43 ` [RFC PATCH] move aic7xxx to pci_request_irq Frederik Deweerdt
2006-10-04 19:44 ` [RFC PATCH] move aic79xx " Frederik Deweerdt
2006-10-04 19:46 ` [RFC PATCH] move tg3 " Frederik Deweerdt
2006-10-04 19:46 ` [RFC PATCH] move e1000 " Frederik Deweerdt
2006-10-04 19:50 ` [RFC PATCH] add pci_{request,free}_irq take #3 Jeff Garzik
2006-10-04 20:29 ` Frederik Deweerdt
2006-10-04 20:33 ` Matthew Wilcox [this message]
2006-10-04 21:26 ` Frederik Deweerdt
2006-10-05 13:59 ` Alexey Dobriyan
2006-10-05 14:36 ` Frederik Deweerdt
2006-10-06 10:04 ` Alexey Dobriyan
2006-10-06 10:31 ` Frederik Deweerdt
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=20061004203311.GI28596@parisc-linux.org \
--to=matthew@wil.cx \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=deweerdt@free.fr \
--cc=gregkh@suse.de \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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