From: Andrew Morton <akpm@linux-foundation.org>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: page_alloc: remove unneeded header files
Date: Tue, 30 May 2023 15:13:06 -0700 [thread overview]
Message-ID: <20230530151306.b9f24b247c66ea7f80df6be8@linux-foundation.org> (raw)
In-Reply-To: <20230527100728.267992-1-linmiaohe@huawei.com>
On Sat, 27 May 2023 18:07:28 +0800 Miaohe Lin <linmiaohe@huawei.com> wrote:
> Remove some unneeded header files. No functional change intended.
>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
> ---
> mm/page_alloc.c | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index e671c747892f..beb6db613238 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -24,9 +24,7 @@
> #include <linux/kernel.h>
> #include <linux/kasan.h>
> #include <linux/kmsan.h>
> -#include <linux/module.h>
This contains the prototype for print_modules(). So we're now reliant
upon module.h being included via some other header, which is fragile.
> #include <linux/suspend.h>
> -#include <linux/pagevec.h>
> #include <linux/ratelimit.h>
> #include <linux/oom.h>
> #include <linux/topology.h>
> @@ -36,8 +34,6 @@
> #include <linux/memory_hotplug.h>
> #include <linux/nodemask.h>
> #include <linux/vmstat.h>
> -#include <linux/sort.h>
> -#include <linux/pfn.h>
> #include <linux/fault-inject.h>
> #include <linux/compaction.h>
> #include <trace/events/kmem.h>
> @@ -52,11 +48,9 @@
> #include <linux/memcontrol.h>
> #include <linux/ftrace.h>
> #include <linux/lockdep.h>
> -#include <linux/nmi.h>
> #include <linux/psi.h>
> #include <linux/khugepaged.h>
> #include <linux/delayacct.h>
> -#include <asm/div64.h>
Needed for do_div()?
> #include "internal.h"
> #include "shuffle.h"
> #include "page_reporting.h"
> --
> 2.27.0
prev parent reply other threads:[~2023-05-30 22:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 10:07 Miaohe Lin
2023-05-30 22:13 ` Andrew Morton [this message]
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=20230530151306.b9f24b247c66ea7f80df6be8@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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