From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Linux-Next Mailing List <linux-next@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org
Cc: pasha.tatashin@soleen.com,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>, Michal Hocko <mhocko@suse.com>,
david@redhat.com, osalvador@suse.de,
Dan Williams <dan.j.williams@intel.com>,
Sasha Levin <sashal@kernel.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Peter Zijlstra <peterz@infradead.org>,
Mel Gorman <mgorman@suse.de>,
Matthew Wilcox <willy@infradead.org>,
David Rientjes <rientjes@google.com>,
John Hubbard <jhubbard@nvidia.com>,
Ira Weiny <ira.weiny@intel.com>,
James Morris <jmorris@namei.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [next] mm/gup.c:96:10: error: implicit declaration of function 'is_zero_pfn' [-Werror,-Wimplicit-function-declaration]
Date: Tue, 2 Feb 2021 20:01:54 +0530 [thread overview]
Message-ID: <CA+G9fYszbxo4giipD0_sV3XHKaq2zVq97rXoyjWf18k5oYEX4Q@mail.gmail.com> (raw)
Linux next tag 20210202 arm, riscv and sh builds with allnoconfig and
tinyconfig failed due to build errors.
make --silent --keep-going --jobs=8
O=/home/tuxbuild/.cache/tuxmake/builds/1/tmp ARCH=arm
CROSS_COMPILE=arm-linux-gnueabihf- 'HOSTCC=sccache clang' 'CC=sccache
clang' zImage
mm/gup.c:96:10: error: implicit declaration of function 'is_zero_pfn'
[-Werror,-Wimplicit-function-declaration]
!is_pinnable_page(page)))
^
include/linux/mm.h:1133:3: note: expanded from macro 'is_pinnable_page'
is_zero_pfn(page_to_pfn(page)))
^
mm/gup.c:96:10: note: did you mean 'is_zero_ino'?
include/linux/mm.h:1133:3: note: expanded from macro 'is_pinnable_page'
is_zero_pfn(page_to_pfn(page)))
^
include/linux/fs.h:3045:20: note: 'is_zero_ino' declared here
static inline bool is_zero_ino(ino_t ino)
^
1 error generated.
Reported-by: Naresh Kamboju <naresh.kamboju@linaro.org>
steps to reproduce:
--------------------------
# TuxMake is a command line tool and Python library that provides
# portable and repeatable Linux kernel builds across a variety of
# architectures, toolchains, kernel configurations, and make targets.
#
# TuxMake supports the concept of runtimes.
# See https://docs.tuxmake.org/runtimes/, for that to work it requires
# that you install podman or docker on your system.
#
# To install tuxmake on your system globally:
# sudo pip3 install -U tuxmake
#
# See https://docs.tuxmake.org/ for complete documentation.
tuxmake --runtime podman --target-arch arm --toolchain clang-11
--kconfig allnoconfig
build details:
https://builds.tuxbuild.com/1nv9wkY1T8wug0sEw2kwuFKLxhK/
Regressions found on sh:
- build/gcc-10-allnoconfig
- build/gcc-9-tinyconfig
- build/gcc-8-allnoconfig
- build/gcc-10-tinyconfig
- build/gcc-9-allnoconfig
- build/gcc-8-tinyconfig
Regressions found on riscv:
- build/gcc-10-allnoconfig
- build/clang-11-tinyconfig
- build/clang-10-allnoconfig
- build/clang-11-allnoconfig
- build/gcc-9-tinyconfig
- build/gcc-8-allnoconfig
- build/gcc-10-tinyconfig
- build/clang-10-tinyconfig
- build/gcc-9-allnoconfig
- build/gcc-8-tinyconfig
Regressions found on arm:
- build/gcc-10-allnoconfig
- build/clang-11-tinyconfig
- build/clang-10-allnoconfig
- build/clang-11-allnoconfig
- build/gcc-9-tinyconfig
- build/gcc-8-allnoconfig
- build/gcc-10-tinyconfig
- build/clang-10-tinyconfig
- build/gcc-9-allnoconfig
- build/gcc-8-tinyconfig
- Naresh
next reply other threads:[~2021-02-02 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 14:31 Naresh Kamboju [this message]
2021-02-02 15:03 ` Pavel Tatashin
2021-02-04 0:56 ` Andrew Morton
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=CA+G9fYszbxo4giipD0_sV3XHKaq2zVq97rXoyjWf18k5oYEX4Q@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=geert@linux-m68k.org \
--cc=ira.weiny@intel.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=mingo@redhat.com \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@soleen.com \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
--cc=sashal@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