Mike Frysinger wrote:
On 9/1/07, Bill Davidsen <[email protected]> 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
That's exactly the point I was making, if your tests and any others
people feel are useful were in a module and/or could be run as init code
only when wanted, everyone could benefit from the tests. Anything
related to build sanity could be in one place, to guard against
surprises like new versions of gcc, typos in patches, etc.
--
bill davidsen <[email protected]>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
