I'm sorry, it seems I am mistaken. This was in reference to patches which
weren't committed.
Please see:
http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2014-October/060203.html
for the patch with this specific mask used.
The reason __GFP_HIGHMEM may have been chosen is
On 02/20/2016 07:15 PM, Derek Yerger wrote:
From drivers/staging/android TODO file - sparse errors.
The current code attempts assignment of -1 to unsigned type gfp_t.
Assignment should be an enumerated type of GFP_KERNEL, GFP_ATOMIC,
GFP_HIGHMEM, or __GFP_HIGH.
The original 2014 patch by Gioh
From drivers/staging/android TODO file - sparse errors.
The current code attempts assignment of -1 to unsigned type gfp_t.
Assignment should be an enumerated type of GFP_KERNEL, GFP_ATOMIC,
GFP_HIGHMEM, or __GFP_HIGH.
The original 2014 patch by Gioh Kim adding debugfs support to android/ion
