mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Imran Khan <kimran@codeaurora.org>
Cc: kbuild-all@01.org, andy.gross@linaro.org, lee.jones@linaro.org,
	Imran Khan <kimran@codeaurora.org>,
	David Brown <david.brown@linaro.org>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:ARM/QUALCOMM SUPPORT" <linux-arm-msm@vger.kernel.org>,
	"open list:ARM/QUALCOMM SUPPORT" <linux-soc@vger.kernel.org>
Subject: Re: [RESEND,PATCH v7 1/2] soc: qcom: Add SoC info driver
Date: Thu, 5 Jan 2017 17:31:05 +0800	[thread overview]
Message-ID: <201701051710.ACYmO1YH%fengguang.wu@intel.com> (raw)
In-Reply-To: <1483514058-10586-1-git-send-email-kimran@codeaurora.org>

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

Hi Imran,

[auto build test WARNING on linus/master]
[also build test WARNING on v4.10-rc2]
[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/Imran-Khan/soc-qcom-Add-SoC-info-driver/20170105-002914
config: arm64-allyesconfig (attached as .config)
compiler: aarch64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
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
        # save the attached .config to linux build tree
        make.cross ARCH=arm64 

All warnings (new ones prefixed by >>):

>> WARNING: drivers/built-in.o(.text+0x472870): Section mismatch in reference from the function qcom_socinfo_init() to the function .init.text:of_flat_dt_get_machine_name()
   The function qcom_socinfo_init() references
   the function __init of_flat_dt_get_machine_name().
   This is often because qcom_socinfo_init lacks a __init
   annotation or the annotation of of_flat_dt_get_machine_name 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: 53644 bytes --]

      reply	other threads:[~2017-01-05  9:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04  7:13 Imran Khan
2017-01-05  9:31 ` 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=201701051710.ACYmO1YH%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=andy.gross@linaro.org \
    --cc=david.brown@linaro.org \
    --cc=kbuild-all@01.org \
    --cc=kimran@codeaurora.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-soc@vger.kernel.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

all inboxes | Powered by JetHome®