From: Tang Chen <tangchen@cn.fujitsu.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (akpm tree related)
Date: Mon, 21 Jan 2013 15:17:06 +0800 [thread overview]
Message-ID: <50FCEB72.1040507@cn.fujitsu.com> (raw)
In-Reply-To: <20130121170804.8b6eec010e00a6cbbcbad66f@canb.auug.org.au>
Hi Stephen,
On 01/21/2013 02:08 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (arm defconfig)
> failed like this:
>
> mm/memblock.c: In function 'memblock_find_in_range_node':
> mm/memblock.c:104:2: error: invalid use of undefined type 'struct movablecore_map'
> mm/memblock.c:123:4: error: invalid use of undefined type 'struct movablecore_map'
> mm/memblock.c:130:7: error: invalid use of undefined type 'struct movablecore_map'
> mm/memblock.c:131:4: error: invalid use of undefined type 'struct movablecore_map'
>
> Caused by commit "page_alloc: bootmem limit with movablecore_map" from
> the akpm tree. The definition of struct movablecore_map is protected by
> CONFIG_HAVE_MEMBLOCK_NODE_MAP but its use is not.
>
> I have reverted that commit for today.
Thank you very much for reporting this. It was my mistake to miss this
definition.
I will post a new version of "page_alloc: bootmem limit with
movablecore_map" since
you have reverted it.
CONFIG_HAVE_MEMBLOCK_NODE_MAP is selected by x86=y, but I don't have any
non-x86 box.
So I didn't test it. Please tell me if you have any problem with it on
other platforms.
Thanks. :)
next prev parent reply other threads:[~2013-01-21 7:17 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 6:08 linux-next: build failure after merge of the final tree (akpm tree related) Stephen Rothwell
2013-01-21 7:17 ` Tang Chen [this message]
2013-01-21 7:25 ` [PATCH v2 1/1] page_alloc: Bootmem limit with movablecore_map Tang Chen
-- strict thread matches above, loose matches on Subject: below --
2013-06-06 7:25 linux-next: build failure after merge of the final tree (akpm tree related) Stephen Rothwell
2013-06-06 7:15 Stephen Rothwell
2013-06-06 6:18 Stephen Rothwell
2013-03-04 3:28 Stephen Rothwell
2013-03-04 9:22 ` Jan Kara
2013-03-04 3:10 Stephen Rothwell
2013-03-06 23:52 ` Andrew Morton
2013-01-24 5:54 Stephen Rothwell
2013-01-24 10:30 ` Shaohua Li
2013-01-24 23:22 ` Stephen Rothwell
2012-11-09 4:16 Stephen Rothwell
2012-11-09 4:09 Stephen Rothwell
2012-11-14 22:18 ` Andrew Morton
2012-11-14 22:30 ` David Miller
2012-11-14 23:09 ` Andrew Morton
2012-11-14 23:10 ` David Miller
2012-11-09 3:58 Stephen Rothwell
2012-11-09 4:01 ` Andrew Morton
2012-11-12 0:00 ` Stephen Rothwell
2012-09-17 11:49 Stephen Rothwell
2012-09-13 8:11 Stephen Rothwell
2012-09-13 13:24 ` David Fries
2012-09-13 13:34 ` Stephen Rothwell
2012-09-14 4:20 ` David Fries
2012-09-13 8:01 Stephen Rothwell
2012-09-13 10:01 ` Shaohua Li
2012-09-13 12:29 ` Stephen Rothwell
2012-05-11 6:20 Stephen Rothwell
2012-03-14 23:44 Stephen Rothwell
2012-02-17 10:20 Stephen Rothwell
2012-02-17 12:06 ` Konstantin Khlebnikov
2012-02-19 23:04 ` Stephen Rothwell
2012-02-19 23:15 ` Andrew Morton
2012-02-17 5:30 Stephen Rothwell
2012-02-17 6:07 ` Benjamin Herrenschmidt
2012-01-20 2:02 Stephen Rothwell
2011-12-17 4:42 Stephen Rothwell
2011-12-17 5:02 ` NeilBrown
2011-11-30 4:52 Stephen Rothwell
2011-11-30 5:40 ` David Miller
2011-11-30 6:07 ` Andrew Morton
2011-11-30 11:48 ` Neil Horman
2011-11-30 4:42 Stephen Rothwell
2011-11-30 5:16 ` Andrew Morton
2011-10-05 8:23 Stephen Rothwell
2011-09-30 1:52 Stephen Rothwell
2011-09-28 10:01 Stephen Rothwell
2011-07-27 3:55 Stephen Rothwell
2011-07-01 5:45 Stephen Rothwell
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=50FCEB72.1040507@cn.fujitsu.com \
--to=tangchen@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).