From: Jan Ceuleers <jan.ceuleers@computer•org>
To: netdev@vger•kernel.org
Subject: Re: [PATCH] Stop scaring users with "treason uncloaked!"
Date: Fri, 19 Dec 2008 10:40:16 +0100 [thread overview]
Message-ID: <494B6C00.2090603@computer.org> (raw)
In-Reply-To: <20081218231407.4096a64e@lxorguk.ukuu.org.uk>
Alan Cox wrote:
>> $ 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.
/usr/src/linux# fgrep -r " on fire" *
arch/i386/kernel/cpu/mcheck/p5.c: printk(KERN_EMERG
"CPU#%d: Possible thermal failure (CPU on fire ?).\n", smp_processor_id());
drivers/macintosh/therm_windtunnel.c: { 1, 0xfffff, 1 } /* on
fire */
drivers/char/lp.c: printk(KERN_INFO "lp%d on
fire\n", minor);
drivers/net/eexpress.c: "board on fire"));
include/asm-sparc64/solerrno.h:#define SOL_ENETDOWN 127 /* Your
subnet is on fire */
include/asm-sparc/solerrno.h:#define SOL_ENETDOWN 127 /* Your
subnet is on fire */
next prev parent reply other threads:[~2008-12-19 9:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 22:16 [PATCH] Stop scaring users with "treason uncloaked!" 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 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
2008-12-19 9:40 ` Jan Ceuleers [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=494B6C00.2090603@computer.org \
--to=jan.ceuleers@computer$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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