From: David Miller <davem@davemloft.net>
To: alan@lxorguk.ukuu.org.uk
Cc: herbert@gondor.apana.org.au, mpm@selenic.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] Stop scaring users with "treason uncloaked!"
Date: Thu, 18 Dec 2008 16:07:46 -0800 (PST) [thread overview]
Message-ID: <20081218.160746.58836056.davem@davemloft.net> (raw)
In-Reply-To: <20081218231407.4096a64e@lxorguk.ukuu.org.uk>
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Date: Thu, 18 Dec 2008 23:14:07 +0000
> On Fri, 19 Dec 2008 10:02:53 +1100
> Herbert Xu <herbert@gondor.apana.org.au> wrote:
>
> > Well
> >
> > $ grep fire drivers/char/lp.c
> > printk(KERN_INFO "lp%d on fire\n", minor);
>
> Interesting. It got changed and then the change got lost between 2.2 and
> 2.4 somewhere. It was changed to report
>
> "lp0 reported invalid error status (on fire, eh?)"
>
> and it looks like that needs re-fixing.
This is just proof that it doesn't matter. If it got lost in
2.4.x that means it's been like this forever as far as %99
of current systems are concerned.
I'm all for seriousness, but if we can't have some comedic license
with a few kernel log messages then the fun of kernel development
truly suffers :-)
next prev parent reply other threads:[~2008-12-19 0:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 22:16 Matt Mackall
2008-12-18 22:33 ` Ilpo Järvinen
2008-12-18 22:36 ` Herbert Xu
2008-12-18 23:50 ` Matt Mackall
2008-12-19 0:15 ` David Miller
2008-12-19 3:49 ` Matt Mackall
2008-12-19 3:54 ` David Miller
2008-12-19 18:13 ` markus reichelt
2008-12-19 0:08 ` David Miller
2008-12-18 22:44 ` Herbert Xu
2008-12-18 22:49 ` Alan Cox
2008-12-18 23:02 ` Herbert Xu
2008-12-18 23:14 ` Alan Cox
2008-12-19 0:07 ` David Miller [this message]
2008-12-18 23:06 ` Matt Mackall
2008-12-19 0:45 ` David Schwartz
2008-12-19 0:55 ` Krzysztof Halasa
2008-12-19 0:58 ` Rick Jones
2009-01-26 17:46 ` Lennart Sorensen
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=20081218.160746.58836056.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=netdev@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
all inboxes | Powered by JetHome®