From: akpm@linux-foundation.org
To: mgorman@techsingularity.net, mm-commits@vger.kernel.org, vbabka@suse.cz
Subject: [folded-merged] mm-page_alloc-add-a-bulk-page-allocator-fix-fix-fix.patch removed from -mm tree
Date: Thu, 29 Apr 2021 22:33:33 -0700 [thread overview]
Message-ID: <20210430053333.njG-o8N-z%akpm@linux-foundation.org> (raw)
The patch titled
Subject: mm/page_alloc: add a bulk page allocator -fix -fix -fix
has been removed from the -mm tree. Its filename was
mm-page_alloc-add-a-bulk-page-allocator-fix-fix-fix.patch
This patch was dropped because it was folded into mm-page_alloc-add-a-bulk-page-allocator.patch
------------------------------------------------------
From: Mel Gorman <mgorman@techsingularity.net>
Subject: mm/page_alloc: add a bulk page allocator -fix -fix -fix
Vlastimil Babka noted that a comment is wrong, fix it. This is the third
fix to the mmotm patch mm-page_alloc-add-a-bulk-page-allocator.patch.
Link: https://lkml.kernel.org/r/20210412110255.GV3697@techsingularity.net
Signed-off-by: Mel Gorman <mgorman@techsingularity.net>
Cc: Vlastimil Babka <vbabka@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/page_alloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/page_alloc.c~mm-page_alloc-add-a-bulk-page-allocator-fix-fix-fix
+++ a/mm/page_alloc.c
@@ -5048,7 +5048,7 @@ unsigned long __alloc_pages_bulk(gfp_t g
return 0;
gfp = alloc_gfp;
- /* Find an allowed local zone that meets the high watermark. */
+ /* Find an allowed local zone that meets the low watermark. */
for_each_zone_zonelist_nodemask(zone, z, ac.zonelist, ac.highest_zoneidx, ac.nodemask) {
unsigned long mark;
_
Patches currently in -mm which might be from mgorman@techsingularity.net are
mm-page_alloc-rename-alloced-to-allocated.patch
mm-page_alloc-add-a-bulk-page-allocator.patch
mm-page_alloc-add-an-array-based-interface-to-the-bulk-page-allocator.patch
mm-memory_hotplug-make-unpopulated-zones-pcp-structures-unreachable-during-hot-remove.patch
reply other threads:[~2021-04-30 5:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210430053333.njG-o8N-z%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mm-commits@vger.kernel.org \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.