From: Greg KH <greg@kroah.com>
To: Dave Jones <davej@redhat.com>,
bk@suse.de, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Bus hidden behind transparent bridge.
Date: Thu, 7 Jun 2007 22:01:04 -0700 [thread overview]
Message-ID: <20070608050104.GB18123@kroah.com> (raw)
In-Reply-To: <20070606063311.GD20745@redhat.com>
On Wed, Jun 06, 2007 at 02:33:11AM -0400, Dave Jones wrote:
> We've had this printk in drivers/pci/probe.c asking people
> to report it if they see it to linux-kernel for a long time.
>
> google finds hundreds of instances of this being hit.
> There are a bunch in bugzilla too..
>
> http://bugzilla.kernel.org/show_bug.cgi?id=6783
> http://bugzilla.kernel.org/show_bug.cgi?id=7403
> http://bugzilla.kernel.org/show_bug.cgi?id=7575
> http://bugzilla.kernel.org/show_bug.cgi?id=7664
> http://bugzilla.kernel.org/show_bug.cgi?id=8074
> http://bugzilla.kernel.org/show_bug.cgi?id=8480
>
> (possibly others, these are just a quick skim based on summary)
>
> I don't recall ever seeing anything happen any time someone has
> reported this. Is it worth keeping the printk there?
> It only seems to cause confusion (users think its an error,
> especially as we ask them to do something).
>
> Better yet, I don't think I've seen a report of this where
> the user is actually experiencing a problem.
>
> Who is the intended recipient of these reports?
They should all go to bk@suse.de as he is the one who added that line.
In fact, if he doesn't fix it up soon, I'm really tempted to just add
his email address there instead, as I'm really tired of getting these
emails and he said it would be fixed up by now...
thanks,
greg k-h
next prev parent reply other threads:[~2007-06-08 5:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 6:33 Bus hidden behind transparent bridge Dave Jones
2007-06-08 5:01 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-02 15:05 bus " Martin Weber
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=20070608050104.GB18123@kroah.com \
--to=greg@kroah.com \
--cc=bk@suse.de \
--cc=davej@redhat.com \
--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