public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.59 morse code panics
Date: 31 Jan 2003 16:34:55 +0100	[thread overview]
Message-ID: <p73hebpqqn4.fsf@oldwotan.suse.de> (raw)
In-Reply-To: Alan Cox's message of "31 Jan 2003 15:20:11 +0100"

Alan Cox <alan@lxorguk.ukuu.org.uk> writes:

> On Fri, 2003-01-31 at 13:22, Dave Jones wrote:
> > Or you could put down the crackpipe and run a serial console between
> > the two boxes. Or even netconsole would make more sense
> > (and be a lot more reliable).
> 
> A lot of newer laptops do not have serial ports. While morse code may
> be a little silly the general purpose hook  it needs to be done 
> cleanly is considerably more useful

And how many users and how many kernel hackers are able to decode
morse on the fly? Are you going to explain to users
"to debug this you'll need to learn morse" ?

If you want to make debugging easy for laptops write a USB or firewire
console. Firewire is actually quite interesting because it can even
do DMA, so you could peek into the memory.

Morse is not helpful.

I admit I was the on who got this ball running by suggesting it "as an 
exercise for the reader" in the original panic blink code, but
guys this was intended as a JOKE, not serious. Please get over it
and don't merge that silly code.

Thanks,
-Andi

       reply	other threads:[~2003-01-31 15:25 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030131104326.GF12286@louise.pinerecords.com.suse.lists.linux.kernel>
     [not found] ` <200301311112.h0VBCv00000575@darkstar.example.net.suse.lists.linux.kernel>
     [not found]   ` <20030131132221.GA12834@codemonkey.org.uk.suse.lists.linux.kernel>
     [not found]     ` <1044025785.1654.13.camel@irongate.swansea.linux.org.uk.suse.lists.linux.kernel>
2003-01-31 15:34       ` Andi Kleen [this message]
2003-01-31 15:41         ` [PATCH] 2.5.59 morse code panics Tomas Szepe
2003-01-31 16:01           ` John Bradford
2003-01-31 16:11             ` Tomas Szepe
2003-01-31 16:17               ` John Bradford
2003-01-31 19:52             ` Horst von Brand
2003-01-31 20:04               ` John Bradford
2003-01-31 21:08                 ` Eric Weigle
2003-01-31 21:14                   ` John Bradford
2003-02-02 15:42             ` Bill Davidsen
2003-02-03 19:14               ` Jos Hulzink
2003-02-03 21:29                 ` Bill Davidsen
2003-02-04  6:00             ` Peter C. Norton
2003-02-07 15:51               ` Ryan Anderson
2003-02-07 16:39                 ` John Bradford
2003-01-31 15:46         ` Dave Jones
2003-01-31 15:55           ` Valdis.Kletnieks
2003-02-03 15:50         ` Pavel Machek
2003-02-04 16:32           ` Henning P. Schmiedehausen
2003-02-05 17:56 Marcelo Roberto Jimenez
  -- strict thread matches above, loose matches on Subject: below --
2003-01-31 21:31 Albert D. Cahalan
2003-01-30 15:07 Tomas Szepe
2003-01-30 17:36 ` Dave Jones
2003-01-30 18:45   ` Alan Cox
2003-01-31 10:43     ` Tomas Szepe
2003-01-31 11:12       ` John Bradford
2003-01-31 13:22         ` Dave Jones
2003-01-31 14:40           ` Valdis.Kletnieks
2003-01-31 14:58             ` John Bradford
2003-01-31 15:05             ` Dave Jones
2003-01-31 15:32               ` Valdis.Kletnieks
2003-01-31 15:09           ` Alan Cox
2003-01-31 14:29             ` John Bradford
2003-01-31 15:13               ` Dave Jones
2003-01-31 15:12             ` Dave Jones
2003-01-31 15:27               ` John Bradford
2003-01-31 15:21           ` Scott Robert Ladd
2003-01-31 17:59     ` Vojtech Pavlik
2003-01-31 18:06       ` Tomas Szepe
2003-01-31 19:38       ` Tomas Szepe

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=p73hebpqqn4.fsf@oldwotan.suse.de \
    --to=ak@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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