mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Separate tainted code from panic code
Date: Thu, 15 Sep 2005 17:06:41 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0509151703450.3743@scrub.home> (raw)
In-Reply-To: <20050915082049.GA29266@mipter.zuzino.mipt.ru>

Hi,

On Thu, 15 Sep 2005, Alexey Dobriyan wrote:

> > Why?  What reason is there for making these changes?
> 
> Most tainted users are in arch/$ARCH/kernel/. The rest including
> kernel.h don't want tainted stuff. And kernel.h is used often.

The tainted definitions don't change very often, they also have no config 
dependencies, so the benefit of separating this is very low.

bye, Roman

      reply	other threads:[~2005-09-15 15:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13 23:07 Alexey Dobriyan
2005-09-14  0:28 ` Andrew Morton
2005-09-15  8:20   ` Alexey Dobriyan
2005-09-15 15:06     ` Roman Zippel [this message]

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=Pine.LNX.4.61.0509151703450.3743@scrub.home \
    --to=zippel@linux-m68k.org \
    --cc=adobriyan@gmail.com \
    --cc=akpm@osdl.org \
    --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

all inboxes | Powered by JetHome®