From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Becky Bruce <becky.bruce@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/2] Move memory size print into common show_cpuinfo for 32-bit
Date: Fri, 10 Oct 2008 15:32:20 +1100 [thread overview]
Message-ID: <1223613140.8157.150.camel@pasglop> (raw)
In-Reply-To: <1222293230-22725-1-git-send-email-becky.bruce@freescale.com>
On Wed, 2008-09-24 at 16:53 -0500, Becky Bruce wrote:
> Most of the platforms were printing the size of the memory
> in their show_cpuinfo implementations. This moves that to
> the common show_cpuinfo, so that all 32-bit platforms will
> now print the size of memory. I also update the code
> to deal with the fact that total_memory is now a phys_addr_t.
Doesn't apply anymore, care to rebase ?
Cheers,
Ben.
next prev parent reply other threads:[~2008-10-10 4:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 21:53 [PATCH 2/2] Move memory size print into common show_cpuinfo for 32-bit Becky Bruce
2008-10-10 4:32 ` Benjamin Herrenschmidt [this message]
2008-10-15 18:25 ` [PATCH] powerpc: " Becky Bruce
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=1223613140.8157.150.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=becky.bruce@freescale.com \
--cc=linuxppc-dev@ozlabs.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).