The patch titled
Subject: mm-improve-__gfp_noretry-comment-based-on-implementation-fix
has been removed from the -mm tree. Its filename was
mm-improve-__gfp_noretry-comment-based-on-implementation-fix.patch
This patch was dropped because it was folded into mm-improve-__gfp_noretry-comment-based-on-implementation.patch
------------------------------------------------------
From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Subject: mm-improve-__gfp_noretry-comment-based-on-implementation-fix
s/has/have/
Cc: David Rientjes <rientjes@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
include/linux/gfp.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN include/linux/gfp.h~mm-improve-__gfp_noretry-comment-based-on-implementation-fix include/linux/gfp.h
--- a/include/linux/gfp.h~mm-improve-__gfp_noretry-comment-based-on-implementation-fix
+++ a/include/linux/gfp.h
@@ -64,8 +64,8 @@ struct vm_area_struct;
* loop around allocator.
*
* __GFP_NORETRY: The VM implementation must not retry indefinitely and will
- * return NULL when direct reclaim and memory compaction has failed to allow the
- * allocation to succeed. The OOM killer is not called with the current
+ * return NULL when direct reclaim and memory compaction have failed to allow
+ * the allocation to succeed. The OOM killer is not called with the current
* implementation.
*
* __GFP_MOVABLE: Flag that this page will be movable by the page migration
_
Patches currently in -mm which might be from akpm@xxxxxxxxxxxxxxxxxxxx are
dax-revert-userfaultfd-change.patch
mm-improve-__gfp_noretry-comment-based-on-implementation.patch
memcg-export-struct-mem_cgroup-fix.patch
memcg-export-struct-mem_cgroup-fix-2.patch
mm-hugetlb-add-cache-of-descriptors-to-resv_map-for-region_add-fix.patch
x86-use-generic-early-mem-copy-fix.patch
mm-mmap-simplify-the-failure-return-working-flow-fix.patch
zswap-dynamic-pool-creation-fix.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
