From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 1/2] Deindentify identify_cpu()
Date: Mon, 23 Feb 2009 07:27:40 -0600 [thread overview]
Message-ID: <1235395660.11996.0.camel@norville.austin.ibm.com> (raw)
In-Reply-To: <689159d7e17a2227e6000b51911750503eed1778.1235355941.git.michael@ellerman.id.au>
On Mon, 2009-02-23 at 13:25 +1100, Michael Ellerman wrote:
> The for-loop body of identify_cpu() has gotten a little big, so move the
> loop body logic into a separate function. No other changes.
>
> Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
Looks good to me.
Acked-by: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
--
David Kleikamp
IBM Linux Technology Center
prev parent reply other threads:[~2009-02-23 13:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 2:25 [PATCH 1/2] Deindentify identify_cpu() Michael Ellerman
2009-02-23 2:25 ` [PATCH 2/2] Make sure we copy all cpu_spec features except PMC related ones Michael Ellerman
2009-02-23 13:28 ` Dave Kleikamp
2009-02-23 13:27 ` Dave Kleikamp [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=1235395660.11996.0.camel@norville.austin.ibm.com \
--to=shaggy@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=paulus@samba.org \
/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).