From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Hugh Dickins <hughd@google.com>
Subject: Re: [linux-next:master] BUILD REGRESSION 19ae1f2bd9c091059f80646604ccef8a1e614f57
Date: Tue, 15 Jun 2021 15:45:44 -0700 [thread overview]
Message-ID: <20210615154544.b22aeff23e9391f0b58cad38@linux-foundation.org> (raw)
In-Reply-To: <60c926d7.tXt5/+3wW2UECP4s%lkp@intel.com>
On Wed, 16 Jun 2021 06:16:55 +0800 kernel test robot <lkp@intel.com> wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> branch HEAD: 19ae1f2bd9c091059f80646604ccef8a1e614f57 Add linux-next specific files for 20210615
>
> Error/Warning ids grouped by kconfigs:
>
> clang_recent_errors
> |-- arm64-randconfig-r014-20210615
> | `-- mm-hugetlb.c:warning:no-previous-prototype-for-function-hugetlb_basepage_index
> |-- x86_64-randconfig-a011-20210615
> | `-- mm-hugetlb.c:warning:no-previous-prototype-for-function-hugetlb_basepage_index
I guess this? Against Hugh's "mm, futex: fix shared futex pgoff on
shmem huge page".
--- a/include/linux/pagemap.h~mm-futex-fix-shared-futex-pgoff-on-shmem-huge-page-fix
+++ a/include/linux/pagemap.h
@@ -535,16 +535,16 @@ static inline pgoff_t page_to_index(stru
return pgoff;
}
+extern pgoff_t hugetlb_basepage_index(struct page *page);
+
/*
* Get the offset in PAGE_SIZE (even for hugetlb pages).
* (TODO: hugetlb pages should have ->index in PAGE_SIZE)
*/
static inline pgoff_t page_to_pgoff(struct page *page)
{
- if (unlikely(PageHuge(page))) {
- extern pgoff_t hugetlb_basepage_index(struct page *page);
+ if (unlikely(PageHuge(page)))
return hugetlb_basepage_index(page);
- }
return page_to_index(page);
}
_
prev parent reply other threads:[~2021-06-15 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 22:16 kernel test robot
2021-06-15 22:45 ` 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=20210615154544.b22aeff23e9391f0b58cad38@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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