Re: [PATCH] mm/memblock: use WARN_ONCE when MAX_NUMNODES passed as input parameter

2014-01-02 Thread David Rientjes
On Mon, 30 Dec 2013, Grygorii Strashko wrote: > > > diff --git a/mm/memblock.c b/mm/memblock.c > > > index 71b11d9..6af873a 100644 > > > --- a/mm/memblock.c > > > +++ b/mm/memblock.c > > > @@ -707,11 +707,9 @@ void __init_memblock __next_free_mem_range(u64 *idx, > > > int nid, > > > stru

Re: [PATCH] mm/memblock: use WARN_ONCE when MAX_NUMNODES passed as input parameter

2013-12-30 Thread Grygorii Strashko
On 12/27/2013 01:45 AM, David Rientjes wrote: On Fri, 20 Dec 2013, Santosh Shilimkar wrote: diff --git a/mm/memblock.c b/mm/memblock.c index 71b11d9..6af873a 100644 --- a/mm/memblock.c +++ b/mm/memblock.c @@ -707,11 +707,9 @@ void __init_memblock __next_free_mem_range(u64 *idx, int nid,

Re: [PATCH] mm/memblock: use WARN_ONCE when MAX_NUMNODES passed as input parameter

2013-12-26 Thread David Rientjes
On Fri, 20 Dec 2013, Santosh Shilimkar wrote: > diff --git a/mm/memblock.c b/mm/memblock.c > index 71b11d9..6af873a 100644 > --- a/mm/memblock.c > +++ b/mm/memblock.c > @@ -707,11 +707,9 @@ void __init_memblock __next_free_mem_range(u64 *idx, int > nid, > struct memblock_type *rsv = &memblo

[PATCH] mm/memblock: use WARN_ONCE when MAX_NUMNODES passed as input parameter

2013-12-20 Thread Santosh Shilimkar
From: Grygorii Strashko Check nid parameter and produce warning if it has deprecated MAX_NUMNODES value. Also re-assign NUMA_NO_NODE value to the nid parameter in this case. These will help to identify the wrong API usage (the caller) and make code simpler. Cc: Yinghai Lu Cc: Tejun Heo Cc: An