From: olof@lixom•net (Olof Johansson)
To: Timur Tabi <timur@freescale•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [PATCH] Update udbg_progress() to display the integer
Date: Mon, 5 Feb 2007 19:30:51 -0600 [thread overview]
Message-ID: <20070206013051.GA15525@lixom.net> (raw)
In-Reply-To: <11707051151024-git-send-email-timur@freescale.com>
On Mon, Feb 05, 2007 at 01:51:55PM -0600, Timur Tabi wrote:
> Although udbg_progress() takes a string and a short as parameters, only
> the string is displayed. This patch also displays the integer, if it's not
> equal to 0xFFFF. This gives callers the option to display only the string.
Some platforms do this already, but they output the numbers first. It's
a good idea to stay consistent with that.
See maple_progress, ps3_progress and friends for templates. They're
quite verbose though.
-Olof
>
> Signed-off-by: Timur Tabi <timur@freescale•com>
> ---
> arch/powerpc/kernel/udbg.c | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/arch/powerpc/kernel/udbg.c b/arch/powerpc/kernel/udbg.c
> index 5730906..c474961 100644
> --- a/arch/powerpc/kernel/udbg.c
> +++ b/arch/powerpc/kernel/udbg.c
> @@ -121,6 +121,11 @@ void udbg_printf(const char *fmt, ...)
> void __init udbg_progress(char *s, unsigned short hex)
> {
> udbg_puts(s);
> + if (hex != 0xffff) {
> + char buf[8];
> + sprintf(buf, " : %04X", hex);
> + udbg_puts(buf);
> + }
> udbg_puts("\n");
> }
>
> --
> 1.4.4
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs•org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
next prev parent reply other threads:[~2007-02-06 1:23 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 [this message]
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
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=20070206013051.GA15525@lixom.net \
--to=olof@lixom$(echo .)net \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=timur@freescale$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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