From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Olof Johansson <olof@lixom.net>,
linuxppc-dev@ozlabs.org, Timur Tabi <timur@freescale.com>
Subject: Re: [PATCH] Update udbg_progress() to display the integer
Date: Wed, 07 Feb 2007 10:38:22 +1100 [thread overview]
Message-ID: <1170805102.2620.264.camel@localhost.localdomain> (raw)
In-Reply-To: <17865.2853.132102.769702@cargo.ozlabs.ibm.com>
> It would have been for the 2-line display on IBM RS/6000 machines. If
> that's still needed, we can put it in arch/powerpc/platforms/chrp
> somewhere, so feel free to remove it from ppc_init().
Do we actually care about this progress stuff ? I've been tempted more
than once to rip it all off... we have console access as early as we can
do progress output on most powerpc platforms nowadays.
If we really want some way of ack'ing that the kernel reached known
known steps with something different than a printk-type interface, then
we should probably have somewhere a list of well defined numeric
constants and use those, but then, I don't like magic numbers.
Ben.
next prev parent reply other threads:[~2007-02-06 23:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 19:51 [PATCH] Update udbg_progress() to display the integer Timur Tabi
2007-02-06 1:30 ` Olof Johansson
2007-02-06 23:08 ` Timur Tabi
2007-02-06 23:11 ` Paul Mackerras
2007-02-06 23:38 ` Benjamin Herrenschmidt [this message]
2007-02-06 23:41 ` Kumar Gala
2007-02-06 23:54 ` Timur Tabi
2007-02-07 0:03 ` Olof Johansson
2007-02-07 0:04 ` Timur Tabi
2007-02-07 21:59 ` Linas Vepstas
2007-02-07 22:26 ` Timur Tabi
2007-02-07 0:00 ` Stephen Rothwell
2007-02-07 0:04 ` Stephen Rothwell
2007-02-06 23:42 ` Timur Tabi
2007-02-07 6:26 ` Mike Strosaker
2007-02-07 16:28 ` Timur Tabi
2007-02-08 0:31 ` Michael Ellerman
2007-02-08 2:07 ` Timur Tabi
2007-02-07 21:03 ` Benjamin Herrenschmidt
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=1170805102.2620.264.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--cc=paulus@samba.org \
--cc=timur@freescale.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;
as well as URLs for NNTP newsgroup(s).