mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bastian Blank <waldi@debian.org>
To: Greg KH <greg@kroah.com>
Cc: Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: RFC: virtualbox tainting.
Date: Fri, 7 Oct 2011 09:03:32 +0200	[thread overview]
Message-ID: <20111007070332.GA13671@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <20111006195824.GA22033@kroah.com>

On Thu, Oct 06, 2011 at 12:58:24PM -0700, Greg KH wrote:
> On Thu, Oct 06, 2011 at 03:50:07PM -0400, Dave Jones wrote:
> > I feel a bit dirty overloading TAINT_CRAP (even if the name is apropos).
> > Should I introduce a TAINT_OUT_OF_TREE perhaps instead ?
> We could do that in a "generic" way by setting a "in-tree" flag type
> thing for everything that is built from within the kernel build, and
> then taint if that flag is not found.

Debian uses such a patch[1] since some time.

Bastian

[1]:
http://anonscm.debian.org/viewvc/kernel/dists/trunk/linux-2.6/debian/patches/debian/module-bug-Add-TAINT_OOT_MODULE-flag.patch?revision=16914&view=markup
-- 
Only a fool fights in a burning house.
		-- Kank the Klingon, "Day of the Dove", stardate unknown

  parent reply	other threads:[~2011-10-07  7:10 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06 19:05 Dave Jones
2011-10-06 19:44 ` Greg KH
2011-10-06 19:50   ` Dave Jones
2011-10-06 19:53     ` Valdis.Kletnieks
2011-10-06 20:03       ` Dave Jones
2011-10-06 20:06       ` Greg KH
2011-10-06 19:58     ` Greg KH
2011-10-06 20:04       ` Dave Jones
2011-10-06 20:30         ` Greg KH
2011-10-07  8:01         ` Jiri Kosina
2011-10-07 10:02           ` Alan Cox
2011-10-07 16:04           ` Valdis.Kletnieks
2011-10-07 17:01             ` Greg KH
2011-10-07 17:46               ` Dave Jones
2011-10-07  7:03       ` Bastian Blank [this message]
2011-10-07 14:40 ` Frank Mehnert
2011-10-07 15:10   ` Dave Jones
2011-10-09 20:12     ` Frank Mehnert
2011-10-07 15:16   ` Josh Boyer
2011-10-07 16:22     ` Valdis.Kletnieks
2011-10-07 18:10       ` Josh Boyer
2011-10-07 18:33         ` Valdis.Kletnieks
2011-10-10  7:58   ` Pekka Enberg
2011-10-10  8:25     ` Dave Airlie
2011-10-10 14:24     ` Greg KH
2011-10-10 16:35       ` Pekka Enberg
2011-10-10 16:49         ` Dave Airlie
2011-10-10 16:51           ` Pekka Enberg
2011-10-10  8:41 ` Maarten Lankhorst
2011-10-10 11:42   ` Josh Boyer
2011-10-12  0:57 ` Parag Warudkar
2011-10-12  7:55   ` Alex Riesen
2011-10-12 14:08     ` Parag Warudkar
2011-10-12 14:18       ` Alex Riesen
2011-10-12 15:00         ` Parag Warudkar
2011-10-12 19:55   ` Zan Lynx
2011-10-12 20:54     ` Parag Warudkar

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=20111007070332.GA13671@wavehammer.waldi.eu.org \
    --to=waldi@debian.org \
    --cc=davej@redhat.com \
    --cc=greg@kroah.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

Powered by JetHome