From: Pekka Enberg <penberg@iki.fi>
To: Tang Chen <tangchen@cn.fujitsu.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
yinghai@kernel.org, jacob.shin@amd.com, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Use memblock_set_current_limit() to set limit for memblock.
Date: Wed, 14 Aug 2013 09:27:57 +0300 [thread overview]
Message-ID: <520B236D.7030704@iki.fi> (raw)
In-Reply-To: <1376451844-15682-1-git-send-email-tangchen@cn.fujitsu.com>
On 8/14/13 6:44 AM, Tang Chen wrote:
> In setup_arch() of x86, it set memblock.current_limit directly.
> We should use memblock_set_current_limit(). If the implementation
> is changed, it is easy to maintain.
>
> Signed-off-by: Tang Chen <tangchen@cn.fujitsu.com>
Reviewed-by: Pekka Enberg <penberg@kernel.org>
prev parent reply other threads:[~2013-08-14 6:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 3:44 [PATCH] x86: Use memblock_set_current_limit() to set limit for memblock Tang Chen
2013-08-14 4:39 ` [tip:x86/mm] " tip-bot for Tang Chen
2013-08-14 6:27 ` Pekka Enberg [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=520B236D.7030704@iki.fi \
--to=penberg@iki.fi \
--cc=hpa@zytor.com \
--cc=jacob.shin@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tangchen@cn.fujitsu.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@kernel.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).