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,
	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: [PATCH v2] soc: qcom: Add SoC info driver
Date: Fri, 28 Oct 2016 00:51:48 +0800	[thread overview]
Message-ID: <201610280010.bwi9O5gs%fengguang.wu@intel.com> (raw)
In-Reply-To: <1477560155-17044-1-git-send-email-kimran@codeaurora.org>

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

Hi Imran,

[auto build test ERROR on linus/master]
[also build test ERROR on v4.9-rc2 next-20161027]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]

url:    https://github.com/0day-ci/linux/commits/Imran-Khan/soc-qcom-Add-SoC-info-driver/20161027-223213
config: arm-multi_v7_defconfig (attached as .config)
compiler: arm-linux-gnueabi-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=arm 

All errors (new ones prefixed by >>):

   drivers/built-in.o: In function `qcom_smem_probe':
>> sunxi_sid.c:(.text+0x113160): undefined reference to `qcom_socinfo_init'
>> sunxi_sid.c:(.text+0x1132d8): undefined reference to `setup_dummy_socinfo'

---
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: 39281 bytes --]

  parent reply	other threads:[~2016-10-27 16:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-27  9:22 Imran Khan
2016-10-27 16:47 ` kbuild test robot
2016-10-27 16:51 ` kbuild test robot [this message]
2016-10-27 20:05 ` Linus Walleij
2016-11-02 10:03   ` Imran Khan

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=201610280010.bwi9O5gs%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=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

Powered by JetHome