From: Greg KH <greg@kroah.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org, andrew.grover@intel.com,
len.brown@intel.com
Subject: Re: [patch] remove mount_root_failed_msg()
Date: Wed, 20 Aug 2003 16:41:14 -0700 [thread overview]
Message-ID: <20030820234114.GA5518@kroah.com> (raw)
In-Reply-To: <20030820232045.GA25921@gtf.org>
On Wed, Aug 20, 2003 at 07:20:45PM -0400, Jeff Garzik wrote:
>
> * overall, I disagree with adding messages like this. The number one
> bug report, by far, for networking drivers is ACPI-related (no
> interrupts delivered). You don't see me adding "boot with acpi=off"
> messages to the net subsystem.
It's the number one bug report for USB drivers too :(
It has gotten smaller, and I would hope that is due to advances in the
ACPI code, but they still do crop up quite frequently.
thanks,
greg k-h
next prev parent reply other threads:[~2003-08-20 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 23:20 [patch] remove mount_root_failed_msg() Jeff Garzik
2003-08-20 23:41 ` Greg KH [this message]
2003-08-21 8:43 ` [PATCH][2.5] fix 'pci=noacpi' was: " Thomas Schlichter
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=20030820234114.GA5518@kroah.com \
--to=greg@kroah.com \
--cc=andrew.grover@intel.com \
--cc=jgarzik@pobox.com \
--cc=len.brown@intel.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