linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Anju T Sudhakar <anju@linux.vnet.ibm.com>
Cc: kbuild-all@01.org, mpe@ellerman.id.au,
	linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	ego@linux.vnet.ibm.com, bsingharora@gmail.com,
	benh@kernel.crashing.org, paulus@samba.org, anton@samba.org,
	sukadev@linux.vnet.ibm.com, mikey@neuling.org,
	stewart@linux.vnet.ibm.com, dja@axtens.net, eranian@google.com,
	hemant@linux.vnet.ibm.com, maddy@linux.vnet.ibm.com,
	anju@linux.vnet.ibm.com
Subject: Re: [PATCH v7 07/10] powerpc/perf: PMU functions for Core IMC and hotplugging
Date: Thu, 20 Apr 2017 05:44:41 +0800	[thread overview]
Message-ID: <201704200528.wqNAfJy4%fengguang.wu@intel.com> (raw)
In-Reply-To: <1492534910-7991-8-git-send-email-anju@linux.vnet.ibm.com>

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

Hi Hemant,

[auto build test WARNING on linus/master]
[also build test WARNING on v4.11-rc7]
[cannot apply to next-20170419]
[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/Anju-T-Sudhakar/powerpc-powernv-Data-structure-and-macros-definitions-for-IMC/20170419-015257
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/01org/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+0x164a08): Section mismatch in reference from the function .core_imc_init() to the function .meminit.text:.alloc_pages_exact_nid()
   The function .core_imc_init() references
   the function __meminit .alloc_pages_exact_nid().
   This is often because .core_imc_init lacks a __meminit
   annotation or the annotation of .alloc_pages_exact_nid 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: 52770 bytes --]

  reply	other threads:[~2017-04-19 21:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 17:01 [PATCH v7 00/10] IMC Instrumentation Support Anju T Sudhakar
2017-04-18 17:01 ` [PATCH v7 01/10] powerpc/powernv: Data structure and macros definitions for IMC Anju T Sudhakar
2017-04-18 17:01 ` [PATCH v7 02/10] powerpc/powernv: Autoload IMC device driver module Anju T Sudhakar
2017-04-18 17:01 ` [PATCH v7 03/10] powerpc/powernv: Detect supported IMC units and its events Anju T Sudhakar
2017-04-18 17:01 ` [PATCH v7 4/10] powerpc/perf: Add generic IMC pmu groupand event functions Anju T Sudhakar
2017-04-18 17:01 ` [PATCH v7 05/10] powerpc/perf: IMC pmu cpumask and cpuhotplug support Anju T Sudhakar
2017-04-18 17:01 ` [PATCH v7 06/10] powerpc/powernv: Core IMC events detection Anju T Sudhakar
2017-04-19 14:40   ` kbuild test robot
2017-04-18 17:01 ` [PATCH v7 07/10] powerpc/perf: PMU functions for Core IMC and hotplugging Anju T Sudhakar
2017-04-19 21:44   ` kbuild test robot [this message]
2017-04-18 17:01 ` [PATCH v7 8/10] powerpc/powernv: Thread IMC events detection Anju T Sudhakar
2017-04-18 17:01 ` [PATCH v7 9/10] powerpc/perf: Thread IMC PMU functions Anju T Sudhakar
2017-04-18 17:01 ` [PATCH v7 10/10] powerpc/perf: Thread imc cpuhotplug support Anju T Sudhakar

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=201704200528.wqNAfJy4%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=anju@linux.vnet.ibm.com \
    --cc=anton@samba.org \
    --cc=benh@kernel.crashing.org \
    --cc=bsingharora@gmail.com \
    --cc=dja@axtens.net \
    --cc=ego@linux.vnet.ibm.com \
    --cc=eranian@google.com \
    --cc=hemant@linux.vnet.ibm.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.vnet.ibm.com \
    --cc=mikey@neuling.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.org \
    --cc=stewart@linux.vnet.ibm.com \
    --cc=sukadev@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;
as well as URLs for NNTP newsgroup(s).