Messages in this thread | | | Date | Wed, 9 Jun 1999 14:00:03 +1000 | From | CaT <> | Subject | Re: Profanity in the Linux Kernel?!?!? |
| |
On Tue, Jun 08, 1999 at 10:52:33AM -0700, Barrett G. Lyon wrote: > >This topic came up several times before, and the result is that > >arbitrary censorship of code/comments is not going to happen. The > >only exception is in kernel messages which can reach the user in the > >message logs, and those have been cleaned up. > > Not that I care.. but.. :
Ditto. though I have to wonder at some of these...
> ./net/core/profile.c: printk(KERN_CRIT "Yep, guys... our template for proc_*_read is crappy :-)\n"); > ./drivers/net/sdladrv.c: printk(KERN_ERR "%s: Damn... Adapter won't start!\n", > ./drivers/isdn/isdn_common.c: printk(KERN_ERR "isdn_common: isdn_poll 1 -> what the hell\n"); > ./drivers/isdn/isdn_common.c: printk(KERN_ERR "isdn_common: isdn_poll 2 -> what the hell\n");
Maybe it's just me but where's the profanity?
> ./arch/sparc64/kernel/traps.c: printk("SHIT[%s:%d]: " > ./arch/sparc64/kernel/traps.c: printk("SHIT[%s:%d]: " > ./arch/sparc64/kernel/traps.c: printk("instruction_access_exception: Shit SFSR[%016lx] SFAR[%016lx], going.\n", > ./arch/sparc64/kernel/traps.c: printk("data_access_exception: Shit SFSR[%016lx] SFAR[%016lx], going.\n",
And that's kinda mild at best. probably best to make them more descriptive.
-- CaT (cat@zip.com.au) URL: http://zipper.zip.com.au/dev/null
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |