From: Andi Kleen <andi@firstfloor.org>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-kernel@vger.kernel.org, dzickus@redhat.com
Subject: Re: [PATCH] Add TAINT_HARDWARE_UNSUPPORTED flag
Date: Sat, 19 Jun 2010 10:40:53 +0200 [thread overview]
Message-ID: <87ocf7o1nu.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20100617134654.22523.39845.sendpatchset@prarit.bos.redhat.com> (Prarit Bhargava's message of "Thu, 17 Jun 2010 09:54:45 -0400")
Prarit Bhargava <prarit@redhat.com> writes:
nt\n");
> + if (flag == TAINT_HARDWARE_UNSUPPORTED)
> + printk(KERN_CRIT "WARNING: This system's hardware is "
> + "unsupported.\n");
The problem with such a message in mainline is that it would
imply that other hardware is actually 'supported'
Which is not really true in most cases.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-06-19 8:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 13:54 [PATCH] Add TAINT_HARDWARE_UNSUPPORTED flag Prarit Bhargava
2010-06-17 16:13 ` Randy Dunlap
2010-06-17 19:54 ` Prarit Bhargava
2010-06-17 20:28 ` Randy Dunlap
2010-06-21 19:21 ` Andrew Morton
2010-06-21 19:45 ` Don Zickus
2010-06-21 20:00 ` Andrew Morton
2010-06-21 20:46 ` Don Zickus
2010-06-22 15:34 ` [PATCH v3] " Don Zickus
2010-06-22 15:48 ` Alan Cox
2010-06-22 16:38 ` Matthew Garrett
2010-06-22 16:57 ` Alan Cox
2010-06-22 17:04 ` Matthew Garrett
2010-06-23 3:06 ` Paul Mundt
2010-06-23 3:30 ` Matthew Garrett
2010-06-23 20:00 ` Don Zickus
2010-06-22 18:58 ` [PATCH v4] " Don Zickus
2010-07-06 20:33 ` Don Zickus
2010-07-06 22:18 ` Alan Cox
2010-06-19 8:40 ` Andi Kleen [this message]
2010-06-19 9:30 ` [PATCH] " Alan Cox
2010-06-21 13:26 ` Don Zickus
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=87ocf7o1nu.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=dzickus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
/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.