loongarch.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Feiyang Chen <chris.chenfeiyang@gmail.com>
To: akpm@linux-foundation.org, willy@infradead.org, vbabka@suse.cz,
	songmuchun@bytedance.com
Cc: Feiyang Chen <chenfeiyang@loongson.cn>,
	chenhuacai@kernel.org, chris.chenfeiyang@gmail.com,
	loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: [PATCH] page-flags.h: Fix a missing header include of static_keys.h
Date: Sat, 25 Jun 2022 16:04:23 +0800	[thread overview]
Message-ID: <20220625080423.2797-1-chenfeiyang@loongson.cn> (raw)

The page-flags.h header relies on static keys since commit
a6b40850c442bf ("mm: hugetlb: replace hugetlb_free_vmemmap_enabled
with a static_key"), so make sure to include the header to avoid
compilation errors.

Fixes: a6b40850c442bf ("mm: hugetlb: replace hugetlb_free_vmemmap_enabled with a static_key")
Cc: stable@vger.kernel.org
Signed-off-by: Feiyang Chen <chenfeiyang@loongson.cn>
---
 include/linux/page-flags.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/include/linux/page-flags.h b/include/linux/page-flags.h
index e66f7aa3191d..147b336c7a35 100644
--- a/include/linux/page-flags.h
+++ b/include/linux/page-flags.h
@@ -11,6 +11,7 @@
 #include <linux/mmdebug.h>
 #ifndef __GENERATING_BOUNDS_H
 #include <linux/mm_types.h>
+#include <linux/static_key.h>
 #include <generated/bounds.h>
 #endif /* !__GENERATING_BOUNDS_H */
 
-- 
2.27.0


             reply	other threads:[~2022-06-25  8:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-25  8:04 Feiyang Chen [this message]
2022-06-25  8:49 ` [PATCH] page-flags.h: Fix a missing header include of static_keys.h Muchun Song
2022-06-25  9:04   ` Huacai Chen
2022-06-25 11:16     ` [External] " Muchun Song
2022-06-25 14:00       ` Huacai Chen
2022-06-25 14:07         ` Greg KH
2022-06-25 14:17           ` Huacai Chen
2022-06-25 14:24             ` Greg KH
2022-06-25 14:26               ` Huacai Chen

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=20220625080423.2797-1-chenfeiyang@loongson.cn \
    --to=chris.chenfeiyang@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=chenfeiyang@loongson.cn \
    --cc=chenhuacai@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=songmuchun@bytedance.com \
    --cc=stable@vger.kernel.org \
    --cc=vbabka@suse.cz \
    --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;
as well as URLs for NNTP newsgroup(s).