From: akpm@linux-foundation.org
To: pasha.tatashin@oracle.com, mm-commits@vger.kernel.org
Subject: [folded-merged] mm-initialize-pages-on-demand-during-boot-fix2.patch removed from -mm tree
Date: Wed, 14 Feb 2018 16:16:24 -0800 [thread overview]
Message-ID: <5a84d158.T39CFqXimjeuAyIh%akpm@linux-foundation.org> (raw)
The patch titled
Subject: mm-initialize-pages-on-demand-during-boot-fix2
has been removed from the -mm tree. Its filename was
mm-initialize-pages-on-demand-during-boot-fix2.patch
This patch was dropped because it was folded into mm-initialize-pages-on-demand-during-boot.patch
------------------------------------------------------
From: Pavel Tatashin <pasha.tatashin@oracle.com>
Subject: mm-initialize-pages-on-demand-during-boot-fix2
fix min() type mismatch warning
Link: http://lkml.kernel.org/r/20180212164543.26592-1-pasha.tatashin@oracle.com
Signed-off-by: Pavel Tatashin <pasha.tatashin@oracle.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/page_alloc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN mm/page_alloc.c~mm-initialize-pages-on-demand-during-boot-fix2 mm/page_alloc.c
--- a/mm/page_alloc.c~mm-initialize-pages-on-demand-during-boot-fix2
+++ a/mm/page_alloc.c
@@ -6341,8 +6341,8 @@ void __paginginit free_area_init_node(in
* We start only with one section of pages, more pages are added as
* needed until the rest of deferred pages are initialized.
*/
- pgdat->static_init_pgcnt = min(PAGES_PER_SECTION,
- pgdat->node_spanned_pages);
+ pgdat->static_init_pgcnt = min_t(unsigned long, PAGES_PER_SECTION,
+ pgdat->node_spanned_pages);
pgdat->first_deferred_pfn = ULONG_MAX;
#endif
free_area_init_core(pgdat);
_
Patches currently in -mm which might be from pasha.tatashin@oracle.com are
mm-initialize-pages-on-demand-during-boot.patch
mm-memory_hotplug-enforce-block-size-aligned-range-check.patch
x86-mm-memory_hotplug-determine-block-size-based-on-the-end-of-boot-memory.patch
mm-uninitialized-struct-page-poisoning-sanity-checking.patch
mm-memory_hotplug-optimize-memory-hotplug.patch
sparc64-ng4-memset-32-bits-overflow.patch
reply other threads:[~2018-02-15 0:16 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=5a84d158.T39CFqXimjeuAyIh%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=pasha.tatashin@oracle.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).