From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Michael Ellerman" <michael@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 4/4] powerpc: Remove printk-only progress implementations
Date: Thu, 15 Jan 2009 00:26:50 -0700 [thread overview]
Message-ID: <fa686aa40901142326y8a314k41a0fee6b3e6ffe5@mail.gmail.com> (raw)
In-Reply-To: <32db977796782e4d132edb123a64b2437e5ea830.1232001793.git.michael@ellerman.id.au>
On Wed, Jan 14, 2009 at 11:43 PM, Michael Ellerman
<michael@ellerman.id.au> wrote:
> Several platforms implement ppc_md.progress as a simple printk. Now that
> we have the ppc_progress() wrapper which falls back to printk if no
> routine is specified, we can remove all the printk-only progress
> implementations.
>
> This leaves us with iSeries_progress(), rtas_progress() and udbg_progress().
>
> Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
Acked-by: Grant Likely <grant.likely@secretlab.ca>
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
prev parent reply other threads:[~2009-01-15 7:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 6:43 [PATCH 1/4] powerpc: Remove unused ppc64_terminate_msg() Michael Ellerman
2009-01-15 6:43 ` [PATCH 2/4] powerpc: Add ppc_progress() wrapper Michael Ellerman
2009-01-15 7:23 ` Grant Likely
2009-01-15 11:34 ` Paul Mackerras
2009-01-15 23:01 ` Benjamin Herrenschmidt
2009-01-15 23:09 ` Michael Ellerman
2009-01-15 6:43 ` [PATCH 3/4] powerpc: Replace ppc_md.progress() uses with ppc_progress() Michael Ellerman
2009-01-15 7:25 ` Grant Likely
2009-01-15 6:43 ` [PATCH 4/4] powerpc: Remove printk-only progress implementations Michael Ellerman
2009-01-15 7:26 ` Grant Likely [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=fa686aa40901142326y8a314k41a0fee6b3e6ffe5@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
/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).