From: Greg KH <greg@kroah.com>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>,
Bernhard Kaindl <bk@suse.de>
Cc: Miles Lane <miles.lane@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.17-rc5-mm2 -- PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) (try 'pci=assign-busses')
Date: Thu, 1 Jun 2006 14:31:33 -0700 [thread overview]
Message-ID: <20060601213133.GC18948@kroah.com> (raw)
In-Reply-To: <200606012155.16545.s0348365@sms.ed.ac.uk>
On Thu, Jun 01, 2006 at 09:55:16PM +0100, Alistair John Strachan wrote:
> On Thursday 01 June 2006 21:30, Miles Lane wrote:
> > Yes, my machine is a dv1240us HP laptop. The machine appears to be
> > working fine. I haven't tested all the devices, but the ones I am
> > using regularly are all happy campers.
>
> It seems many HP and Compaq notebooks that this problem; I've got the same
> thing on my NC6000 and it works fine too. BIOS problem?
>
> Andrew, I think this message should be silenced (or at least the note about
> LKML) if there's no evidence of breakage. For the last LKML 4-5 reporters,
> they reported no side-affects. At the very least, the message could be toned
> down somewhat.
Bernhard put that message in there for a good reason, let's let him
decide if something needs to change or not.
thanks,
greg k-h
next prev parent reply other threads:[~2006-06-01 21:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 14:52 2.6.17-rc5-mm2 -- PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) (try 'pci=assign-busses') Miles Lane
2006-06-01 16:53 ` Andrew Morton
2006-06-01 21:07 ` Greg KH
2006-06-01 21:35 ` Alessandro Suardi
2006-06-01 19:45 ` Alistair John Strachan
2006-06-01 20:30 ` Miles Lane
2006-06-01 20:55 ` Alistair John Strachan
2006-06-01 21:31 ` Greg KH [this message]
2006-06-01 21:59 ` Alistair John Strachan
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=20060601213133.GC18948@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=bk@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=s0348365@sms.ed.ac.uk \
/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.