From: "Ranjeet Shetye" <ranjeet.shetye@zultys.com>
To: <linux-kernel@vger.kernel.org>
Subject: RE: [STUPID] Best looking code to transfer to a t-shirt
Date: Fri, 3 Jan 2003 16:20:43 -0800 [thread overview]
Message-ID: <001901c2b387$1ea1eb00$0100a8c0@zultys.com> (raw)
In-Reply-To: <20030103233927.GM29422@holomorphy.com>
I vote for "panic ()" in kernel/panic.c
The panic output makes my heart sink everytime single time.
If only the Linux kernel had something as heart-warming as FreeBSD's
"diediedie ()". :D
Ranjeet Shetye
Senior Software Engineer
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of
> William Lee Irwin III
> Sent: Friday, January 03, 2003 3:39 PM
> To: Maciej Soltysiak
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: [STUPID] Best looking code to transfer to a t-shirt
>
>
> On Fri, Jan 03, 2003 at 02:25:09PM +0100, Maciej Soltysiak wrote:
> > I am in a t-shirt transfering frenzy and was wondering
> which part of
> > the kernel code it would be best to have on my t-shirt. I
> was looking
> > at my favourite: netfilter code, but it is to clean, short
> and simple
> > functions, no tons of pointers, no mallocs, no hex numbers,
> too many
> > defines used. I was looking for something terribly complicated and
> > looking awesome to the eye. How about we have a poll of the most
> > frightening pieces of the kernel ? What are your ideas?
>
> sheer bulk: include/asm-ia64/sn/sn2/shub_mmr.h
> most typedefs:
> include/asm-ia64/sn/sn2/shub_mmr_t.h
> bizarre (and ugly) idiom: fs/devfs/*.c
> just plain ugly: arch/i386/kernel/cpu/mtrr/generic.c
> really crusty-looking: drivers/char/*tty*.c
> terrifying ultra-legacyness: drivers/ide/legacy/hd.c
> fishiness: drivers/usb/serial/pl2303.c
> why so much code?: drivers/char/dz.c
> highly cleanup-resistant: mm/slab.c
> unusual preprocessor games: kernel/cpufreq.c
> contrived inefficiency:
> fs/proc/inode.c:proc_fill_super()
>
> Bill
> -
> 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/
next prev parent reply other threads:[~2003-01-04 0:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 13:25 Maciej Soltysiak
2003-01-03 13:26 ` Jose Celestino
2003-01-03 14:55 ` Matthias Schniedermeyer
2003-01-03 15:03 ` Anders Gustafsson
2003-01-03 15:11 ` Tomas Szepe
2003-01-03 15:59 ` Disconnect
2003-01-03 16:32 ` Randy.Dunlap
2003-01-03 16:53 ` Arnaldo Carvalho de Melo
2003-01-03 16:33 ` Alvaro Lopes
2003-01-03 22:58 ` Rik van Riel
2003-01-03 23:39 ` William Lee Irwin III
2003-01-04 0:20 ` Ranjeet Shetye [this message]
2003-01-04 13:46 ` Maciej Soltysiak
2003-01-04 13:47 ` Maciej Soltysiak
2003-01-05 3:55 ` Randy.Dunlap
2003-01-03 14:53 uaca
2003-01-04 0:13 Nivedita Singhvi
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='001901c2b387$1ea1eb00$0100a8c0@zultys.com' \
--to=ranjeet.shetye@zultys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome