From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Jan Beulich <jbeulich@suse.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Andy Lutomirski <luto@amacapital.net>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [-mmots 2016-04-25] hugetlb: error: ‘cpu_has_pse’ undeclared
Date: Wed, 27 Apr 2016 09:37:46 +0900 [thread overview]
Message-ID: <20160427003746.GC4782@swordfish> (raw)
In-Reply-To: <20160426150032.6d97757c25bb4cdfb9a345cf@linux-foundation.org>
On (04/26/16 15:00), Andrew Morton wrote:
> > 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
> > ^
>
> hm, how did that happen. I had some issues with cpu_has_pse a number
> of days ago but they later went away.
>
> In my current tree I have, in arch/x86/include/asm/hugetlb.h:
>
> #define hugepages_supported() boot_cpu_has(X86_FEATURE_PSE)
>
> and that came in from linux-next.patch. I wonder why your tree is
> different.
>
> <looks>
>
> OK, http://ozlabs.org/~akpm/mmots/broken-out/linux-next.patch has no
> changes to arch/x86/include/asm/hugetlb.h at all. Maybe I fat-fingered
> something. Odd.
>
> I have just uploaded a new snapshot - it should be good now. Sorry about
> that.
no worries. thanks!
-ss
next prev parent reply other threads:[~2016-04-27 0:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 14:14 [-mmots 2016-04-25] hugetlb: error: ‘cpu_has_pse’ undeclared Sergey Senozhatsky
2016-04-26 22:00 ` Andrew Morton
2016-04-27 0:37 ` Sergey Senozhatsky [this message]
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=20160427003746.GC4782@swordfish \
--to=sergey.senozhatsky.work@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@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