From: Lee Revell <rlrevell@joe-job.com>
To: Brent Casavant <bcasavan@sgi.com>
Cc: celeron2002@chile.com, linux-kernel@vger.kernel.org
Subject: Re: bug in mm/slab.c
Date: Tue, 23 Nov 2004 19:07:17 -0500 [thread overview]
Message-ID: <1101254837.13549.3.camel@krustophenia.net> (raw)
In-Reply-To: <Pine.SGI.4.58.0411231754430.46250@kzerza.americas.sgi.com>
On Tue, 2004-11-23 at 18:02 -0600, Brent Casavant wrote:
> On Tue, 23 Nov 2004, Lee Revell wrote:
> > Did you see the line about 'module license NVIDIA taints kernel'?
> > Google for what this means and you will understand why this bug report
> > is offtopic.
>
> Not necessarily.
OK, this one was real. But, my point remains valid re: tainted vs
untainted kernels.
Lee
next prev parent reply other threads:[~2004-11-24 0:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 22:13 bug in mm/slab.c celeron2002
2004-11-23 23:02 ` Lee Revell
2004-11-24 0:02 ` Brent Casavant
2004-11-24 0:07 ` Lee Revell [this message]
2004-11-23 23:55 ` Andrew Morton
2004-11-23 23:55 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2007-05-18 5:53 BUG " Jeff Garzik
2007-05-18 6:00 ` Satyam Sharma
2007-05-18 6:04 ` Andrew Morton
2004-11-23 22:12 bug " celeron
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=1101254837.13549.3.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=bcasavan@sgi.com \
--cc=celeron2002@chile.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 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.