linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mike Strosaker <strosake@austin.ibm.com>
Cc: Olof Johansson <olof@lixom.net>,
	linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
	Timur Tabi <timur@freescale.com>
Subject: Re: [PATCH] Update udbg_progress() to display the integer
Date: Thu, 08 Feb 2007 08:03:46 +1100	[thread overview]
Message-ID: <1170882226.2620.291.camel@localhost.localdomain> (raw)
In-Reply-To: <45C97121.9080609@austin.ibm.com>


> Yeah, magic numbers suck, but the op panel does have some physical 
> constraints that prevent the printing of verbose messages.  These codes 
> could be mapped to useful messages in a file in Documentation/powerpc, 
> for example.

Or at least a .h with well defined constants instead of the current
mess :-)

Ben.

      parent reply	other threads:[~2007-02-07 21:04 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
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 [this message]

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=1170882226.2620.291.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    --cc=paulus@samba.org \
    --cc=strosake@austin.ibm.com \
    --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).