linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: 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 v4] Add TAINT_HARDWARE_UNSUPPORTED flag
Date: Tue, 6 Jul 2010 16:33:09 -0400	[thread overview]
Message-ID: <20100706203309.GG5381@redhat.com> (raw)
In-Reply-To: <20100622185812.GC5381@redhat.com>

On Tue, Jun 22, 2010 at 02:58:12PM -0400, Don Zickus wrote:
> This patch reserves taint bits for distributions to use as they seem fit
> without the fear of them being stepped up in future kernels.
> 
> V4:  just reserve the bits

Any acks or naks on this version of the patch?

Cheers,
Don

> 
> Signed-off-by: Don Zickus <dzickus@redhat.com>
> 
> ---
> 
> Not sure if this is sufficient for reserving or if there is some other code
> I have to add elsewhere too.
> 
> diff --git a/include/linux/kernel.h b/include/linux/kernel.h
> index cc5e3ff..c7b9e2c 100644
> --- a/include/linux/kernel.h
> +++ b/include/linux/kernel.h
> @@ -347,6 +347,11 @@ extern enum system_states {
>  #define TAINT_WARN			9
>  #define TAINT_CRAP			10
>  #define TAINT_FIRMWARE_WORKAROUND	11
> +/* Reserving bits for vendor specific uses */
> +#define TAINT_RESERVED28		28
> +#define TAINT_RESERVED29		29
> +#define TAINT_RESERVED30		30
> +#define TAINT_RESERVED31		31
>  
>  extern void dump_stack(void) __cold;
>  

  reply	other threads:[~2010-07-06 20:33 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 [this message]
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=20100706203309.GG5381@redhat.com \
    --to=dzickus@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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;
as well as URLs for NNTP newsgroup(s).