From: David Rientjes <rientjes@google.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
santosh.shilimkar@ti.com, x86@kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Tejun Heo <tj@kernel.org>, Yinghai Lu <yinghai@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86/mm: memblock: switch to use NUMA_NO_NODE
Date: Tue, 14 Jan 2014 17:25:08 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1401141724480.32645@chino.kir.corp.google.com> (raw)
In-Reply-To: <1389198198-31027-1-git-send-email-grygorii.strashko@ti.com>
On Wed, 8 Jan 2014, Grygorii Strashko wrote:
> Update X86 code to use NUMA_NO_NODE instead of MAX_NUMNODES while
> calling memblock APIs, because memblock API is changed to use NUMA_NO_NODE and
> will produce warning during boot otherwise.
>
> See:
> https://lkml.org/lkml/2013/12/9/898
>
> Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Stephen Rothwell <sfr@canb.auug.org.au>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Yinghai Lu <yinghai@kernel.org>
> Cc: David Rientjes <rientjes@google.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
>
> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
Acked-by: David Rientjes <rientjes@google.com>
Thanks for following through with this, Grygorii!
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2014-01-15 1:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 13:36 WARNING: CPU: 0 PID: 0 at mm/memblock.c:789 __next_free_mem_range() Fengguang Wu
2014-01-07 2:25 ` [setup_bios_corruption_check] WARNING: CPU: 0 PID: 0 at mm/memblock.c:789 __next_free_mem_range+0x82/0x261() Fengguang Wu
2014-01-08 16:23 ` [PATCH] x86/mm: memblock: switch to use NUMA_NO_NODE Grygorii Strashko
2014-01-08 17:27 ` Grygorii Strashko
2014-01-08 18:05 ` Santosh Shilimkar
2014-01-15 1:25 ` David Rientjes [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=alpine.DEB.2.02.1401141724480.32645@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=grygorii.strashko@ti.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=santosh.shilimkar@ti.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--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