From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Patrick Mochel <mochel@osdl.org>, Greg KH <greg@kroah.com>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] PCI reorg changes for 2.5.14
Date: Tue, 07 May 2002 23:55:12 -0400 [thread overview]
Message-ID: <3CD8A1A0.6080501@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0205071433570.9905-100000@penguin.transmeta.com>
Linus Torvalds wrote:
>The whole notion of having just _one_ PCI interrupt routing function is
>definitely _broken_.
>
Yeah -- having a per-device interrupt router would be quite useful for
those Via devices we had so much interrupt routing trouble with...
Jeff
prev parent reply other threads:[~2002-05-08 3:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-06 22:25 [BK PATCH] PCI reorg changes for 2.5.14 Greg KH
2002-05-07 9:02 ` Christoph Hellwig
2002-05-07 16:15 ` Ivan Kokshaysky
2002-05-07 16:49 ` Greg KH
2002-05-07 18:27 ` Linus Torvalds
2002-05-07 20:23 ` Greg KH
2002-05-07 21:29 ` Patrick Mochel
2002-05-07 21:50 ` Linus Torvalds
2002-05-07 23:13 ` Patrick Mochel
2002-05-08 3:55 ` Jeff Garzik [this message]
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=3CD8A1A0.6080501@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=greg@kroah.com \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=torvalds@transmeta.com \
/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.