The patch titled
Subject: mm: fix up sparse warning in gfpflags_allow_blocking
has been removed from the -mm tree. Its filename was
mm-fix-up-sparse-warning-in-gfpflags_allow_blocking.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Jeff Layton <jlayton@xxxxxxxxxxxxxxx>
Subject: mm: fix up sparse warning in gfpflags_allow_blocking
sparse says:
include/linux/gfp.h:274:26: warning: incorrect type in return expression (different base types)
include/linux/gfp.h:274:26: expected bool
include/linux/gfp.h:274:26: got restricted gfp_t
...add a forced cast to silence the warning.
Signed-off-by: Jeff Layton <jeff.layton@xxxxxxxxxxxxxxx>
Cc: Mel Gorman <mgorman@xxxxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
include/linux/gfp.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN include/linux/gfp.h~mm-fix-up-sparse-warning-in-gfpflags_allow_blocking include/linux/gfp.h
--- a/include/linux/gfp.h~mm-fix-up-sparse-warning-in-gfpflags_allow_blocking
+++ a/include/linux/gfp.h
@@ -271,7 +271,7 @@ static inline int gfpflags_to_migratetyp
static inline bool gfpflags_allow_blocking(const gfp_t gfp_flags)
{
- return gfp_flags & __GFP_DIRECT_RECLAIM;
+ return (bool __force)(gfp_flags & __GFP_DIRECT_RECLAIM);
}
#ifdef CONFIG_HIGHMEM
_
Patches currently in -mm which might be from jlayton@xxxxxxxxxxxxxxx are
fsnotify-destroy-marks-with-call_srcu-instead-of-dedicated-thread.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
