make GFP_NOTRACK definition unconditional
authorGlauber Costa <glommer@parallels.com>
Mon, 8 Oct 2012 23:33:52 +0000 (16:33 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Tue, 9 Oct 2012 07:23:01 +0000 (16:23 +0900)
commit3e648ebe076390018c317881d7d926f24d7bac6b
treea1ce3f4b196756ac2850b47714f5a1dac6ce52ea
parentbeb51eaa88238daba698ad837222ad277d440b6d
make GFP_NOTRACK definition unconditional

There was a general sentiment in a recent discussion (See
https://lkml.org/lkml/2012/9/18/258) that the __GFP flags should be
defined unconditionally.  Currently, the only offender is GFP_NOTRACK,
which is conditional to KMEMCHECK.

Signed-off-by: Glauber Costa <glommer@parallels.com>
Acked-by: Christoph Lameter <cl@linux.com>
Cc: Mel Gorman <mgorman@suse.de>
Acked-by: David Rientjes <rientjes@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
include/linux/gfp.h