From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Parag Warudkar <parag.warudkar@gmail.com>,
devzero@web.de, Matt.Domsch@dell.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RFC] be more verbose when probing EDD
Date: Mon, 17 Dec 2007 15:27:09 -0800 [thread overview]
Message-ID: <476705CD.4020405@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0712180023310.32270@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Dec 16 2007 20:18, Alan Cox wrote:
>>> Why tax other people with a warning/hang etc. in printk when the
>>> problem is very unlikely on their systems?
>> I think there is sense in it if you do it subtly differently.
>>
>> printk(".. if this hangs do ... \r");
>> edd_stuff();
>> printk(" \r");
>>
>>
>> So that we display it, do the EDD call, then write over it with whatever
>> is next that matters.
>
> Does printk support escape sequences? The last time I tried
> printk("\e[1;35m omg ponies \e[0m"); that did not went too successful.
>
Uh, no. Do that and anyone trying to interpret logs will beat you to
death with a pickled herring.
-hpa
next prev parent reply other threads:[~2007-12-17 23:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 19:11 [PATCH] [RFC] be more verbose when probing EDD devzero
2007-12-16 19:59 ` Parag Warudkar
2007-12-16 20:18 ` Alan Cox
2007-12-17 23:25 ` Jan Engelhardt
2007-12-17 23:27 ` H. Peter Anvin [this message]
2007-12-18 0:10 ` Alan Cox
2007-12-18 0:22 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2007-12-16 21:04 devzero
2007-12-16 21:01 ` Alan Cox
2007-12-16 19:19 devzero
2007-12-16 15:34 devzero
2007-12-16 17:34 ` Parag Warudkar
2007-12-16 18:17 ` H. Peter Anvin
2007-12-22 1:15 ` Andi Kleen
2007-12-22 1:48 ` H. Peter Anvin
2007-12-22 1:57 ` Andi Kleen
2007-12-22 2:22 ` H. Peter Anvin
2007-12-22 2:41 ` Andi Kleen
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=476705CD.4020405@zytor.com \
--to=hpa@zytor.com \
--cc=Matt.Domsch@dell.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=devzero@web.de \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=parag.warudkar@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.