From: kbuild test robot <lkp@intel.com>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [RFC PATCH mmotm] mm/z3fold.c: z3fold_page_isolate() can be static
Date: Fri, 19 Apr 2019 21:09:24 +0800 [thread overview]
Message-ID: <20190419130924.GA161478@ivb42> (raw)
In-Reply-To: <201904192137.KiV8DXsU%lkp@intel.com>
Fixes: eaa5a15c91fe ("mm/z3fold.c: support page migration")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
z3fold.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/mm/z3fold.c b/mm/z3fold.c
index d9eabfda..1ffecd6 100644
--- a/mm/z3fold.c
+++ b/mm/z3fold.c
@@ -1285,7 +1285,7 @@ static u64 z3fold_get_pool_size(struct z3fold_pool *pool)
return atomic64_read(&pool->pages_nr);
}
-bool z3fold_page_isolate(struct page *page, isolate_mode_t mode)
+static bool z3fold_page_isolate(struct page *page, isolate_mode_t mode)
{
struct z3fold_header *zhdr;
struct z3fold_pool *pool;
@@ -1320,8 +1320,8 @@ bool z3fold_page_isolate(struct page *page, isolate_mode_t mode)
return false;
}
-int z3fold_page_migrate(struct address_space *mapping, struct page *newpage,
- struct page *page, enum migrate_mode mode)
+static int z3fold_page_migrate(struct address_space *mapping, struct page *newpage,
+ struct page *page, enum migrate_mode mode)
{
struct z3fold_header *zhdr, *new_zhdr;
struct z3fold_pool *pool;
@@ -1379,7 +1379,7 @@ int z3fold_page_migrate(struct address_space *mapping, struct page *newpage,
return 0;
}
-void z3fold_page_putback(struct page *page)
+static void z3fold_page_putback(struct page *page)
{
struct z3fold_header *zhdr;
struct z3fold_pool *pool;
prev parent reply other threads:[~2019-04-19 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 13:09 [mmotm:master 200/348] mm/z3fold.c:1288:6: sparse: symbol 'z3fold_page_isolate' was not declared. Should it be static? kbuild test robot
2019-04-19 13:09 ` kbuild test robot [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=20190419130924.GA161478@ivb42 \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=vitalywool@gmail.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