From: Yafang Shao <laoar.shao@gmail.com>
To: Jason Yan <yanaijie@huawei.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: make __invalidate_mapping_pages() static
Date: Thu, 15 Oct 2020 14:09:24 +0800 [thread overview]
Message-ID: <CALOAHbB-n7na7WafQsW1Cu_-BaN1Tqbv7Mt+0LyiNbob4YmffQ@mail.gmail.com> (raw)
In-Reply-To: <20201015054808.2445904-1-yanaijie@huawei.com>
On Thu, Oct 15, 2020 at 1:44 PM Jason Yan <yanaijie@huawei.com> wrote:
>
> Fix the following sparse warning:
>
> mm/truncate.c:531:15: warning: symbol '__invalidate_mapping_pages' was
> not declared. Should it be static?
>
> Fixes: eb1d7a65f08a ("mm, fadvise: improve the expensive remote LRU cache draining after FADV_DONTNEED")
> Signed-off-by: Jason Yan <yanaijie@huawei.com>
> ---
> mm/truncate.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/truncate.c b/mm/truncate.c
> index 18cec39a9f53..960edf5803ca 100644
> --- a/mm/truncate.c
> +++ b/mm/truncate.c
> @@ -528,7 +528,7 @@ void truncate_inode_pages_final(struct address_space *mapping)
> }
> EXPORT_SYMBOL(truncate_inode_pages_final);
>
> -unsigned long __invalidate_mapping_pages(struct address_space *mapping,
> +static unsigned long __invalidate_mapping_pages(struct address_space *mapping,
> pgoff_t start, pgoff_t end, unsigned long *nr_pagevec)
> {
> pgoff_t indices[PAGEVEC_SIZE];
> --
> 2.25.4
>
Ah, this new helper is only used in truncate.c, so it should be static.
Thanks for catching it.
Reviewed-by: Yafang Shao <laoar.shao@gmail.com>
--
Thanks
Yafang
prev parent reply other threads:[~2020-10-15 6:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 5:48 [PATCH] mm: make __invalidate_mapping_pages() static Jason Yan
2020-10-15 6:09 ` Yafang Shao [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=CALOAHbB-n7na7WafQsW1Cu_-BaN1Tqbv7Mt+0LyiNbob4YmffQ@mail.gmail.com \
--to=laoar.shao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=yanaijie@huawei.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;
as well as URLs for NNTP newsgroup(s).