From: Andi Kleen <andi@firstfloor.org>
To: Lans Zhang <jia.zhang@windriver.com>
Cc: <mingo@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/mm/numa: fix becoming single node on numa machine with 32-bit kernel.
Date: Fri, 06 Dec 2013 10:22:54 -0800 [thread overview]
Message-ID: <87wqjhvny9.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <1386303510-18574-1-git-send-email-jia.zhang@windriver.com> (Lans Zhang's message of "Fri, 6 Dec 2013 12:18:30 +0800")
Lans Zhang <jia.zhang@windriver.com> writes:
>
> Signed-off-by: Lans Zhang <jia.zhang@windriver.com>
Patch looks good to me.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2013-12-06 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 4:18 [PATCH] x86/mm/numa: fix becoming single node on numa machine with 32-bit kernel Lans Zhang
2013-12-06 18:22 ` Andi Kleen [this message]
2013-12-19 15:42 ` [tip:x86/mm] x86/mm/numa: Fix 32-bit kernel NUMA boot tip-bot for Lans Zhang
2013-12-19 16:44 ` Yinghai Lu
2013-12-20 2:17 ` Lans Zhang
2013-12-20 6:23 ` Yinghai Lu
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=87wqjhvny9.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=jia.zhang@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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