From: Jeff Garzik <jgarzik@pobox.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org
Subject: Re: boot messages
Date: Tue, 22 Apr 2003 11:14:43 -0400 [thread overview]
Message-ID: <20030422151443.GA25026@gtf.org> (raw)
In-Reply-To: <20030422072023.5fa430b6.rddunlap@osdl.org>
On Tue, Apr 22, 2003 at 07:20:23AM -0700, Randy.Dunlap wrote:
> | changed between 2.4 and 2.5. I consider this a bug, and welcome patches
> | to fix it. Note, though, that the recent PCI probe order fixes that
> | went in via Andrew Morton may have addressed this issue for some people.
>
> Patch has already been posted 2 times.
Out of sight, out of mind. :)
I am also wondering how link order and PCI detection order are affecting
things, so re-testing without patches on 2.5.68-bk3 would be useful, for
those having problems.
Re-send the patch against 2.5.68-bk3 if the problem persists...
Jeff
next prev parent reply other threads:[~2003-04-22 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 12:45 boot messages Andries.Brouwer
2003-04-22 13:01 ` Jeff Garzik
2003-04-22 14:20 ` Randy.Dunlap
2003-04-22 15:14 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-22 15:11 Andries.Brouwer
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=20030422151443.GA25026@gtf.org \
--to=jgarzik@pobox.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox