From: Ville Herva <vherva@niksula.hut.fi>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Rodland <arodland@noln.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -ac] Panicking in morse code
Date: Sat, 20 Jul 2002 10:05:36 +0300 [thread overview]
Message-ID: <20020720070536.GE1548@niksula.cs.hut.fi> (raw)
In-Reply-To: <p737kjsuhnj.fsf@oldwotan.suse.de>
On Fri, Jul 19, 2002 at 12:38:24PM +0200, you [Andi Kleen] wrote:
> Andrew Rodland <arodland@noln.com> writes:
>
> > I was researching panic_blink() for someone who needed a little help,
> > when I noticed the comment above the function definition, not being the
> > kind to step down from a challenge (unless it's just really hard), I
> > decided to write morse code output code.
>
> I would consider beeps annoying, but then I usually just cut the beeper
> line on any new PC I install so personally I do not care. Still imagine
> what a machine room that overheated and caused several boxes to panic
> would sound like...
I'm just waiting for Andrew to come up with a proper morse code network
layer, so that the machines in the room can communicate (provided they have
a mic each)... Now combine that with Ingo's network console and...
-- v --
v@iki.fi
next prev parent reply other threads:[~2002-07-20 7:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020719011300.548d72d5.arodland@noln.com.suse.lists.linux.kernel>
2002-07-19 10:38 ` Andi Kleen
2002-07-20 7:05 ` Ville Herva [this message]
2002-07-20 11:49 ` Neale Banks
2002-07-20 11:55 ` Thunder from the hill
[not found] ` <20020720173222.3286fcbb.arodland@noln.com.suse.lists.linux.kernel>
[not found] ` <200207211849.56076.bhards@bigpond.net.au.suse.lists.linux.kernel>
[not found] ` <20020721100818.A22176@flint.arm.linux.org.uk.suse.lists.linux.kernel>
2002-07-21 9:29 ` [PATCH -ac] Panicking in morse code v3 Andi Kleen
2002-07-19 5:13 [PATCH -ac] Panicking in morse code Andrew Rodland
2002-07-19 5:29 ` William Lee Irwin III
2002-07-19 16:36 ` Thorsten Kranzkowski
2002-07-19 17:00 ` Andrew Rodland
2002-07-19 17:27 ` Eli Carter
2002-07-19 17:32 ` Andrew Rodland
2002-07-20 0:35 ` Alan Cox
2002-07-20 0:39 ` Andrew Rodland
2002-07-20 0:48 ` Thunder from the hill
2002-07-25 12:51 ` Bill Davidsen
2002-07-26 3:43 ` Daniel Phillips
2002-07-26 4:47 ` Daniel Phillips
2002-07-26 4:52 ` jdow
2002-07-26 5:13 ` Daniel Phillips
2002-07-26 13:50 ` Bill Davidsen
2002-07-26 13:38 ` Bill Davidsen
2002-07-26 14:39 ` Richard B. Johnson
2002-07-26 20:09 ` Bill Davidsen
2002-07-26 23:25 ` Jens Schmidt
2002-07-27 2:05 ` Albert D. Cahalan
2002-07-27 4:00 ` Andrew Rodland
2002-07-27 4:04 ` Andrew Rodland
2002-07-29 11:50 ` Bill Davidsen
2002-07-29 12:34 ` Richard B. Johnson
2002-07-29 19:57 ` Albert D. Cahalan
2002-07-31 17:54 ` Bill Davidsen
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=20020720070536.GE1548@niksula.cs.hut.fi \
--to=vherva@niksula.hut.fi \
--cc=ak@suse.de \
--cc=arodland@noln.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
all inboxes | Powered by JetHome®