From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, pasha.tatashin@soleen.com,
akpm@linux-foundation.org
Subject: [folded-merged] mm-page_ext-init-page_ext-early-if-there-are-no-deferred-struct-pages-v2.patch removed from -mm tree
Date: Thu, 02 Feb 2023 21:44:27 -0800 [thread overview]
Message-ID: <20230203054428.013EBC433D2@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm-page_ext-init-page_ext-early-if-there-are-no-deferred-struct-pages-v2
has been removed from the -mm tree. Its filename was
mm-page_ext-init-page_ext-early-if-there-are-no-deferred-struct-pages-v2.patch
This patch was dropped because it was folded into mm-page_ext-init-page_ext-early-if-there-are-no-deferred-struct-pages.patch
------------------------------------------------------
From: Pasha Tatashin <pasha.tatashin@soleen.com>
Subject: mm-page_ext-init-page_ext-early-if-there-are-no-deferred-struct-pages-v2
Date: Wed, 18 Jan 2023 15:52:51 +0000
fix build with CONFIG_PAGE_EXTENSION=n
Link: https://lkml.kernel.org/r/20230118155251.2522985-1-pasha.tatashin@soleen.com
Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
--- a/include/linux/page_ext.h~mm-page_ext-init-page_ext-early-if-there-are-no-deferred-struct-pages-v2
+++ a/include/linux/page_ext.h
@@ -29,6 +29,8 @@ struct page_ext_operations {
bool need_shared_flags;
};
+extern bool deferred_struct_pages;
+
#ifdef CONFIG_PAGE_EXTENSION
/*
@@ -54,7 +56,6 @@ struct page_ext {
unsigned long flags;
};
-extern bool deferred_struct_pages;
extern bool early_page_ext;
extern unsigned long page_ext_size;
extern void pgdat_page_ext_init(struct pglist_data *pgdat);
_
Patches currently in -mm which might be from pasha.tatashin@soleen.com are
mm-page_ext-do-not-allocate-space-for-page_ext-flags-if-not-needed.patch
mm-page_ext-init-page_ext-early-if-there-are-no-deferred-struct-pages.patch
reply other threads:[~2023-02-03 5:44 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=20230203054428.013EBC433D2@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=pasha.tatashin@soleen.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 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.