mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Parag Warudkar" <parag.warudkar@gmail.com>
Cc: devzero@web.de, Matt.Domsch@dell.com, hpa@zytor.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RFC] be more verbose when probing EDD
Date: Sun, 16 Dec 2007 20:18:49 +0000	[thread overview]
Message-ID: <20071216201849.24f7aa5f@the-village.bc.nu> (raw)
In-Reply-To: <82e4877d0712161159r2572dbbfi15159c66e4b7e33b@mail.gmail.com>

> 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.

That way you'd only see it when it hung - and that might be worth a patch
and test from someone.

  reply	other threads:[~2007-12-16 20:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-16 19:11 devzero
2007-12-16 19:59 ` Parag Warudkar
2007-12-16 20:18   ` Alan Cox [this message]
2007-12-17 23:25     ` Jan Engelhardt
2007-12-17 23:27       ` H. Peter Anvin
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=20071216201849.24f7aa5f@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=Matt.Domsch@dell.com \
    --cc=devzero@web.de \
    --cc=hpa@zytor.com \
    --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 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®