From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@amacapital.net>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
"linux-mmc@vger.kernel.org Sergey Senozhatsky"
<sergey.senozhatsky@gmail.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: [-mmots 2016-04-25] hugetlb: error: ‘cpu_has_pse’ undeclared
Date: Tue, 26 Apr 2016 23:14:35 +0900 [thread overview]
Message-ID: <20160426141435.GA501@swordfish> (raw)
Hello,
v4.6-rc5-mmots-2016-04-25-17-33
In file included from include/linux/hugetlb.h:418:0,
from fs/hugetlbfs/inode.c:28:
fs/hugetlbfs/inode.c: In function ‘init_hugetlbfs_fs’:
./arch/x86/include/asm/hugetlb.h:7:31: error: ‘cpu_has_pse’ undeclared (first use in this function)
#define hugepages_supported() cpu_has_pse
^
fs/hugetlbfs/inode.c:1325:7: note: in expansion of macro ‘hugepages_supported’
if (!hugepages_supported()) {
^~~~~~~~~~~~~~~~~~~
./arch/x86/include/asm/hugetlb.h:7:31: note: each undeclared identifier is reported only once for each function it appears in
#define hugepages_supported() cpu_has_pse
^
fs/hugetlbfs/inode.c:1325:7: note: in expansion of macro ‘hugepages_supported’
if (!hugepages_supported()) {
^~~~~~~~~~~~~~~~~~~
scripts/Makefile.build:289: recipe for target 'fs/hugetlbfs/inode.o' failed
make[2]: *** [fs/hugetlbfs/inode.o] Error 1
scripts/Makefile.build:440: recipe for target 'fs/hugetlbfs' failed
make[1]: *** [fs/hugetlbfs] Error 2
make[1]: *** Waiting for unfinished jobs....
git grep cpu_has_pse
arch/x86/include/asm/hugetlb.h:#define hugepages_supported() cpu_has_pse
-ss
next reply other threads:[~2016-04-26 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 14:14 Sergey Senozhatsky [this message]
2016-04-26 22:00 ` [-mmots 2016-04-25] hugetlb: error: ‘cpu_has_pse’ undeclared Andrew Morton
2016-04-27 0:37 ` Sergey Senozhatsky
2016-04-27 8:01 ` Ingo Molnar
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=20160426141435.GA501@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jbeulich@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=vkuznets@redhat.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