DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=OgTM6AQEoXQ7svaV5Y/YcFnmtw6iogBooXxuAcbCGkIkBU6ywFVuAERwT4P6zNjDDQwMiPkjw5LkxeSuYvLt1DJE/McAhZQUwvwGcrGmPjixAKxxJy+Pj9fLeSKSpKB+oYJRXrgaE4WtqCmmtBr81YY1qX7riOmY26n15F/ZSj4=
Message-ID: <8bd0f97a0709012044p4e7826e2s46368e519bd349e@mail.gmail.com>
Date: Sat, 1 Sep 2007 23:44:36 -0400
From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Bill Davidsen" <davidsen@tmr.com>
Subject: Re: the Linux kernel, testsuites, and maybe *you*
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>
In-Reply-To: <46DA2133.5000809@tmr.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <8bd0f97a0708311422u309ff09cs24dfe64ff535a982@mail.gmail.com>
	 <46DA2133.5000809@tmr.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 896
Lines: 17

On 9/1/07, Bill Davidsen <davidsen@tmr.com> wrote:
> If you want to test that stuff and run it on the current code in the
> kernel, how about a kernel module? You could "modprobe sanitytest" or
> something and report to syslog at module load time. And maybe have a
> parameter which does something drastic if something core is so hosed
> that filesystem damage is likely. Or just optional init code run by a
> kernel option, perhaps sanity testing after boot is not a great idea.

i'm fully capable of doing my own testing right now; that isnt the
point of this thread ... the point is for everyone to benefit, not
just the Blackfin architecture
-mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/