From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Andrew Morton <akpm@linux-foundation.org>,
open list <linux-kernel@vger.kernel.org>
Cc: Roman Gushchin <guro@fb.com>,
andreas.schaufler@gmx.de,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Mike Kravetz <mike.kravetz@oracle.com>,
Michal Hocko <mhocko@kernel.org>, Rik van Riel <riel@surriel.com>,
js1304@gmail.com, lkft-triage@lists.linaro.org
Subject: mm/hugetlb.c:5580:3: error: implicit declaration of function 'for_each_mem_pfn_range'; did you mean 'for_each_mem_range'
Date: Mon, 6 Apr 2020 19:48:54 +0530 [thread overview]
Message-ID: <CA+G9fYtfG4nZs0ON=bBNarPaycNOgGNvhXxcdrGzM1epDDBt7A@mail.gmail.com> (raw)
While building Linux-next master for arm beagle board x15 the following
build error was noticed.
mm/hugetlb.c: In function 'hugetlb_cma_reserve':
mm/hugetlb.c:5580:3: error: implicit declaration of function
'for_each_mem_pfn_range'; did you mean 'for_each_mem_range'?
[-Werror=implicit-function-declaration]
for_each_mem_pfn_range(i, nid, &start_pfn, &end_pfn, NULL) {
^~~~~~~~~~~~~~~~~~~~~~
for_each_mem_range
mm/hugetlb.c:5580:62: error: expected ';' before '{' token
for_each_mem_pfn_range(i, nid, &start_pfn, &end_pfn, NULL) {
^
Few more details about build test,
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y
CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
# CONFIG_TRANSPARENT_HUGEPAGE is not set
# CONFIG_CMA is not set
Kernel config link,
http://snapshots.linaro.org/openembedded/lkft/lkft/sumo/intel-core2-32/lkft/linux-mainline/2591/config
Build log,
https://ci.linaro.org/view/lkft/job/openembedded-lkft-linux-next/DISTRO=lkft,MACHINE=am57xx-evm,label=docker-lkft/743/consoleText
--
Linaro LKFT
https://lkft.linaro.org
next reply other threads:[~2020-04-06 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 14:18 Naresh Kamboju [this message]
2020-04-06 17:25 ` mm/hugetlb.c:5580:3: error: implicit declaration of function 'for_each_mem_pfn_range'; did you mean 'for_each_mem_range' Roman Gushchin
2020-04-09 22:06 ` Yang Li
2020-04-10 16:19 ` Roman Gushchin
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+G9fYtfG4nZs0ON=bBNarPaycNOgGNvhXxcdrGzM1epDDBt7A@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=andreas.schaufler@gmx.de \
--cc=guro@fb.com \
--cc=js1304@gmail.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=riel@surriel.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).