mm, gfp: escalatedly define GFP_HIGHUSER and GFP_HIGHUSER_MOVABLE
authorJianyu Zhan <[email protected]>
Sat, 13 Dec 2014 00:55:43 +0000 (16:55 -0800)
committerLinus Torvalds <[email protected]>
Sat, 13 Dec 2014 20:42:48 +0000 (12:42 -0800)
commit2d48366b3ff745729815c15077508f8d7722ec5f
tree290f887e7b6e25d5c41d78084f4b08abd8b2df58
parent66f2ca7e3f59312888131546176b42d6e248558a
mm, gfp: escalatedly define GFP_HIGHUSER and GFP_HIGHUSER_MOVABLE

GFP_USER, GFP_HIGHUSER and GFP_HIGHUSER_MOVABLE are escalatedly confined
defined, also implied by their names:

GFP_USER                                  = GFP_USER
GFP_USER + __GFP_HIGHMEM                  = GFP_HIGHUSER
GFP_USER + __GFP_HIGHMEM + __GFP_MOVABLE  = GFP_HIGHUSER_MOVABLE

So just make GFP_HIGHUSER and GFP_HIGHUSER_MOVABLE escalatedly defined to
reflect this fact.  It also makes the definition clear and texturally warn
on any furture break-up of this escalated relastionship.

Signed-off-by: Jianyu Zhan <[email protected]>
Acked-by: Johannes Weiner <[email protected]>
Acked-by: Kirill A. Shutemov <[email protected]>
Acked-by: David Rientjes <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
include/linux/gfp.h