linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Laura Abbott <lauraa@codeaurora.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [mmotm:master 10/417] mm/page_alloc.c:5033:38: error: 'ARCH_PFN_OFFSET' undeclared
Date: Sat, 24 Jan 2015 07:23:17 -0800	[thread overview]
Message-ID: <54C3B8E5.7010002@codeaurora.org> (raw)
In-Reply-To: <201501240940.uDGVjj95%fengguang.wu@intel.com>

On 1/23/2015 5:35 PM, kbuild test robot wrote:
> tree:   git://git.cmpxchg.org/linux-mmotm.git master
> head:   c64429bcc60a702f19f5cfdb5c39277863278a8c
> commit: c2ae2ed329b6b540ea2cbf75a7d14f7ff194b296 [10/417] mm/page_alloc.c: don't offset memmap for flatmem
> config: mn10300-asb2364_defconfig (attached as .config)
> reproduce:
>    wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
>    chmod +x ~/bin/make.cross
>    git checkout c2ae2ed329b6b540ea2cbf75a7d14f7ff194b296
>    # save the attached .config to linux build tree
>    make.cross ARCH=mn10300
>
> All error/warnings:
>
>     mm/page_alloc.c: In function 'alloc_node_mem_map':
>>> mm/page_alloc.c:5033:38: error: 'ARCH_PFN_OFFSET' undeclared (first use in this function)
>          offset = pgdat->node_start_pfn - ARCH_PFN_OFFSET;
>                                           ^
>     mm/page_alloc.c:5033:38: note: each undeclared identifier is reported only once for each function it appears in
>
> vim +/ARCH_PFN_OFFSET +5033 mm/page_alloc.c
>
>    5027		 */
>    5028		if (pgdat == NODE_DATA(0)) {
>    5029			mem_map = NODE_DATA(0)->node_mem_map;
>    5030	#if defined(CONFIG_HAVE_MEMBLOCK_NODE_MAP) || defined(CONFIG_FLATMEM)
>    5031			if (page_to_pfn(mem_map) != pgdat->node_start_pfn) {
>    5032				if (IS_ENABLED(CONFIG_HAVE_MEMBLOCK_NODE_MAP))
>> 5033					offset = pgdat->node_start_pfn - ARCH_PFN_OFFSET;
>    5034				mem_map -= offset;
>    5035			}
>    5036	#endif /* CONFIG_HAVE_MEMBLOCK_NODE_MAP || CONFIG_FLATMEM */
>
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> http://lists.01.org/mailman/listinfo/kbuild                 Intel Corporation
>

Andrew, can you drop this patch from mmotm for now? Vlastimil still had
some questions and I'm going to be on vacation next week.

Thanks,
Laura

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2015-01-24 15:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-24  1:35 [mmotm:master 10/417] mm/page_alloc.c:5033:38: error: 'ARCH_PFN_OFFSET' undeclared kbuild test robot
2015-01-24 15:23 ` Laura Abbott [this message]

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=54C3B8E5.7010002@codeaurora.org \
    --to=lauraa@codeaurora.org \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.org \
    /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).