From: Jeff Garzik <jgarzik@pobox.com>
To: "Leech, Christopher" <christopher.leech@intel.com>
Cc: "H. J. Lu" <hjl@lucon.org>, linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: PCI device order problem
Date: Thu, 24 Oct 2002 20:31:21 -0400 [thread overview]
Message-ID: <3DB890D9.8070506@pobox.com> (raw)
In-Reply-To: BD9B60A108C4D511AAA10002A50708F2073175F7@orsmsx118.jf.intel.com
There is also the pci=nosort kernel command line parameter.
next prev parent reply other threads:[~2002-10-25 0:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 0:21 PCI device order problem Leech, Christopher
2002-10-25 0:31 ` Jeff Garzik [this message]
2002-10-25 0:40 ` H. J. Lu
-- strict thread matches above, loose matches on Subject: below --
2002-10-25 0:25 Leech, Christopher
2002-10-25 0:39 ` H. J. Lu
2002-10-24 23:39 H. J. Lu
2002-10-24 23:49 ` Jeff Garzik
2002-10-24 23:56 ` H. J. Lu
2002-10-25 0:14 ` Jeff Garzik
2002-10-25 0:18 ` H. J. Lu
2002-10-25 10:00 ` Alan Cox
2002-10-25 16:11 ` H. J. Lu
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=3DB890D9.8070506@pobox.com \
--to=jgarzik@pobox.com \
--cc=christopher.leech@intel.com \
--cc=hjl@lucon.org \
--cc=linux-kernel@vger.kernel.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 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).