From: Andi Kleen <andi@firstfloor.org>
To: Muli Ben-Yehuda <muli@il.ibm.com>
Cc: "Keshavamurthy, Anil S" <anil.s.keshavamurthy@intel.com>,
Robert Hancock <hancockr@shaw.ca>, Zan Lynx <zlynx@acm.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, "Raj, Ashok" <ashok.raj@intel.com>
Subject: Re: 2.6.22-rc6-mm1 Intel DMAR crash on AMD x86_64
Date: 30 Jun 2007 21:50:47 +0200 [thread overview]
Message-ID: <p73645543xk.fsf@bingen.suse.de> (raw)
In-Reply-To: <20070629162343.GD27698@rhun.ibm.com>
Muli Ben-Yehuda <muli@il.ibm.com> writes:
>
> The convention is to print a KERN_DEBUG message if hardware is not
> found when probing it, otherwise the boot messages become cluttered
> with lots of "$FOO not found".
No the convention is to print no message at all when nothing is found
Some drivers fail this, but they're bad examples.
-Andi
next prev parent reply other threads:[~2007-06-30 18:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.GKNLH/oj9PSCnQCxx9ZAggjc5uA@ifi.uio.no>
[not found] ` <fa.WYdi9Gj/0/XomcQpW4CEW5a4kKI@ifi.uio.no>
2007-06-29 0:58 ` 2.6.22-rc6-mm1 Intel DMAR crash on AMD x86_64 Robert Hancock
2007-06-29 1:14 ` Li, Shaohua
2007-06-29 15:28 ` Keshavamurthy, Anil S
2007-06-29 16:23 ` Muli Ben-Yehuda
2007-06-29 19:23 ` Keshavamurthy, Anil S
2007-06-29 21:18 ` Muli Ben-Yehuda
2007-06-30 19:50 ` Andi Kleen [this message]
2007-06-29 21:56 ` Rafael J. Wysocki
2007-07-14 7:22 ` 2.6.22-rc6-mm1 Robert Hancock
2007-07-14 9:07 ` 2.6.22-rc6-mm1 Andrew Morton
2007-07-14 18:23 ` 2.6.22-rc6-mm1 Thomas Gleixner
2007-06-28 10:43 2.6.22-rc6-mm1 Andrew Morton
2007-06-28 20:40 ` 2.6.22-rc6-mm1 Intel DMAR crash on AMD x86_64 Zan Lynx
2007-06-28 23:50 ` Zach Carter
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=p73645543xk.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=ashok.raj@intel.com \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=muli@il.ibm.com \
--cc=zlynx@acm.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 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.