From: Matthew Garrett <mjg@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Don Zickus <dzickus@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Prarit Bhargava <prarit@redhat.com>,
linux-kernel@vger.kernel.org,
Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: [PATCH v3] Add TAINT_HARDWARE_UNSUPPORTED flag
Date: Tue, 22 Jun 2010 17:38:17 +0100 [thread overview]
Message-ID: <20100622163817.GE20668@srcf.ucam.org> (raw)
In-Reply-To: <20100622164835.4ddb9432@lxorguk.ukuu.org.uk>
On Tue, Jun 22, 2010 at 04:48:35PM +0100, Alan Cox wrote:
> > + printk(KERN_CRIT "UNSUPPORTED HARDWARE DEVICE: %s\n", msg);
> > + WARN_TAINT(1, TAINT_HARDWARE_UNSUPPORTED,
> > + "Your hardware is unsupported. Please do not report "
> > + "bugs, panics, oopses, etc., on this hardware.\n");
>
> And as already pointed out it's not unsupported hardware even in the case
> you described
It's hardware that isn't supported by the vendor. How is it not
unsupported hardware in that context?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-06-22 16:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 13:54 [PATCH] " 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 [this message]
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 ` [PATCH] " Andi Kleen
2010-06-19 9:30 ` 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=20100622163817.GE20668@srcf.ucam.org \
--to=mjg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dzickus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=randy.dunlap@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome