[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <201705311852.P4eg2x0G%fengguang.wu@intel.com>
Date: Wed, 31 May 2017 18:17:07 +0800
From: kbuild test robot <lkp@...el.com>
To: Michal Hocko <mhocko@...nel.org>
Cc: kbuild-all@...org, Andrew Morton <akpm@...ux-foundation.org>,
Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
Mel Gorman <mgorman@...e.de>, linux-mm@...ck.org,
LKML <linux-kernel@...r.kernel.org>,
Michal Hocko <mhocko@...e.com>
Subject: Re: [PATCH] mm: consider memblock reservations for deferred memory
initialization sizing
Hi Michal,
[auto build test WARNING on mmotm/master]
[also build test WARNING on v4.12-rc3 next-20170530]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Michal-Hocko/mm-consider-memblock-reservations-for-deferred-memory-initialization-sizing/20170531-153111
base: git://git.cmpxchg.org/linux-mmotm.git master
config: x86_64-acpi-redef (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
>> WARNING: mm/built-in.o(.text+0x3cbaa): Section mismatch in reference from the function memblock_reserved_memory_within() to the variable .meminit.data:memblock
The function memblock_reserved_memory_within() references
the variable __meminitdata memblock.
This is often because memblock_reserved_memory_within lacks a __meminitdata
annotation or the annotation of memblock is wrong.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
Download attachment ".config.gz" of type "application/gzip" (29923 bytes)
Powered by blists - more mailing lists