From: Junjie Fu <fujunjie1@qq.com>
To: linux-mm@kvack.org, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, willy@infradead.org,
mhocko@suse.com, gourry@gourry.net, Junjie Fu <fujunjie1@qq.com>
Subject: [PATCH] mempolicy.h: Remove unnecessary header file inclusions
Date: Fri, 6 Dec 2024 23:53:49 +0800 [thread overview]
Message-ID: <tencent_08B979048FE091821B290B18AE97E70DC507@qq.com> (raw)
Originally, linux/mempolicy.h included linux/pagemap.h because vma_migratable()
was implemented inline within the header, requiring mapping_gfp_mask()
function to implement vma_migratable(). Now that vma_migratable() is only
declared in linux/mempolicy.h and its implementation has been moved to mempolicy.c,
the inclusion of linux/pagemap.h in the header is no longer necessary.
Additionally, since mempolicy.c includes internal.h, and internal.h already
includes linux/pagemap.h, so there is no need to modify mempolicy.c after
removing the direct inclusion of linux/pagemap.h from linux/mempolicy.h
Signed-off-by: Junjie Fu <fujunjie1@qq.com>
---
include/linux/mempolicy.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/linux/mempolicy.h b/include/linux/mempolicy.h
index ce9885e0178a..d36877557b00 100644
--- a/include/linux/mempolicy.h
+++ b/include/linux/mempolicy.h
@@ -12,7 +12,6 @@
#include <linux/rbtree.h>
#include <linux/spinlock.h>
#include <linux/nodemask.h>
-#include <linux/pagemap.h>
#include <uapi/linux/mempolicy.h>
struct mm_struct;
--
2.34.1
next reply other threads:[~2024-12-06 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 15:53 Junjie Fu [this message]
2024-12-07 6:00 ` Andrew Morton
2024-12-07 8:14 ` [PATCH] mm/mempolicy.c: include pagemap.h directly Junjie Fu
2024-12-07 17:14 ` Matthew Wilcox
2024-12-07 18:22 ` [PATCH] mm/mempolicy.c: include pagemap.h directly in right place Junjie Fu
2024-12-07 19:53 ` [PATCH] mempolicy.h: Remove unnecessary header file inclusions SeongJae Park
2024-12-07 21:55 ` Matthew Wilcox
2024-12-08 13:50 ` Junjie Fu
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=tencent_08B979048FE091821B290B18AE97E70DC507@qq.com \
--to=fujunjie1@qq.com \
--cc=akpm@linux-foundation.org \
--cc=gourry@gourry.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=willy@infradead.org \
/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