From: kbuild test robot <lkp@intel.com>
To: Michael Bringmann <mwb@linux.vnet.ibm.com>
Cc: kbuild-all@01.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>,
Michael Bringmann <mwb@linux.vnet.ibm.com>,
John Allen <jallen@linux.vnet.ibm.com>,
Nathan Fontenot <nfont@linux.vnet.ibm.com>,
Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
Thomas Falcon <tlfalcon@linux.vnet.ibm.com>
Subject: Re: [PATCH V3 2/2] pseries/initnodes: Ensure nodes initialized for hotplug
Date: Wed, 25 Oct 2017 04:26:02 +0800 [thread overview]
Message-ID: <201710250328.5xkGn2LB%fengguang.wu@intel.com> (raw)
In-Reply-To: <8d171641-b2ed-77f4-fc3f-2b5e4a56c4e8@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]
Hi Michael,
[auto build test WARNING on powerpc/next]
[also build test WARNING on v4.14-rc6 next-20171018]
[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/Michael-Bringmann/pseries-nodes-Ensure-enough-nodes-avail-for-operations/20171024-021023
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
config: powerpc-allyesconfig (attached as .config)
compiler: powerpc64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=powerpc
All warnings (new ones prefixed by >>):
>> WARNING: vmlinux.o(.text+0x820e0): Section mismatch in reference from the function .numa_update_cpu_topology() to the function .init.text:.setup_node_data()
The function .numa_update_cpu_topology() references
the function __init .setup_node_data().
This is often because .numa_update_cpu_topology lacks a __init
annotation or the annotation of .setup_node_data is wrong.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 55158 bytes --]
prev parent reply other threads:[~2017-10-24 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 13:45 [PATCH V3 0/2] pseries/nodes: Fix issues with memoryless nodes Michael Bringmann
2017-10-23 13:46 ` [PATCH V3 1/2] pseries/nodes: Ensure enough nodes avail for operations Michael Bringmann
2017-10-23 13:46 ` [PATCH V3 2/2] pseries/initnodes: Ensure nodes initialized for hotplug Michael Bringmann
2017-10-24 20:26 ` kbuild test robot [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=201710250328.5xkGn2LB%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=jallen@linux.vnet.ibm.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=mwb@linux.vnet.ibm.com \
--cc=nfont@linux.vnet.ibm.com \
--cc=tlfalcon@linux.vnet.ibm.com \
--cc=tyreld@linux.vnet.ibm.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
all inboxes | Powered by JetHome®