linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-next@vger.kernel.org,
	nacc@linux.vnet.ibm.com, Richard Weinberger <richard@nod.at>
Subject: Re: mmotm 2014-04-22-15-20 uploaded (uml 32- and 64-bit defconfigs)
Date: Wed, 23 Apr 2014 10:48:27 -0700	[thread overview]
Message-ID: <5357FCEB.2060507@infradead.org> (raw)
In-Reply-To: <20140423134131.778f0d0a@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]

On 04/23/14 10:41, Luiz Capitulino wrote:
> On Wed, 23 Apr 2014 10:10:29 -0700
> Randy Dunlap <rdunlap@infradead.org> wrote:
> 
>> On 04/22/14 15:21, akpm@linux-foundation.org wrote:
>>> The mm-of-the-moment snapshot 2014-04-22-15-20 has been uploaded to
>>>
>>>    http://www.ozlabs.org/~akpm/mmotm/
>>>
>>> mmotm-readme.txt says
>>>
>>> README for mm-of-the-moment:
>>>
>>> http://www.ozlabs.org/~akpm/mmotm/
>>>
>>> This is a snapshot of my -mm patch queue.  Uploaded at random hopefully
>>> more than once a week.
>>>
>>> You will need quilt to apply these patches to the latest Linus release (3.x
>>> or 3.x-rcY).  The series file is in broken-out.tar.gz and is duplicated in
>>> http://ozlabs.org/~akpm/mmotm/series
>>>
>>
>> include/linux/hugetlb.h:468:9: error: 'HPAGE_SHIFT' undeclared (first use in this function)
> 
> The patch adding HPAGE_SHIFT usage to hugetlb.h in current mmotm is this:
> 
> http://www.ozlabs.org/~akpm/mmotm/broken-out/hugetlb-ensure-hugepage-access-is-denied-if-hugepages-are-not-supported.patch
> 
> But I can't reproduce the issue to be sure what the problem is. Are you
> building the kernel on 32bits? Can you provide the output of
> "grep -i huge .config" or send your .config in private?
> 

[adding Richard to cc:]


As in $subject, if I build uml x86 32-bit or 64-bit defconfig, the build fails with
this error.

> grep -i huge UM64/.config
# CONFIG_HUGETLB_PAGE is not set


Full x86_64 uml defconfig is attached.

Thanks,
-- 
~Randy

[-- Attachment #2: um64.config --]
[-- Type: application/x-config, Size: 23546 bytes --]

  reply	other threads:[~2014-04-23 17:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22 22:21 mmotm 2014-04-22-15-20 uploaded akpm
2014-04-23 17:10 ` mmotm 2014-04-22-15-20 uploaded (uml 32- and 64-bit defconfigs) Randy Dunlap
2014-04-23 17:41   ` Luiz Capitulino
2014-04-23 17:48     ` Randy Dunlap [this message]
2014-04-23 18:16       ` Luiz Capitulino
2014-04-23 18:20         ` Randy Dunlap
2014-04-23 18:24         ` Andrew Morton
2014-04-23 19:24           ` Nishanth Aravamudan
2014-04-23 22:10           ` Stephen Rothwell
2014-04-23 22:18             ` Andrew Morton
2014-04-23 22:31               ` Stephen Rothwell
2014-04-23 22:41                 ` Andrew Morton
2014-04-24  0:00                 ` Randy Dunlap
2014-04-23 23:31             ` Nishanth Aravamudan

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=5357FCEB.2060507@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=lcapitulino@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nacc@linux.vnet.ibm.com \
    --cc=richard@nod.at \
    /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).