linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Peter Chen <hzpeterchen@gmail.com>
Cc: kbuild-all@01.org, Bjorn Andersson <bjorn.andersson@linaro.org>,
	Li Yang <leoli@freescale.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>, Peter Chen <Peter.Chen@nxp.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Rajesh Bhagat <rajesh.bhagat@nxp.com>,
	linux@arm.linux.org.uk
Subject: Re: [PATCH 1/1] usb: chipidea: add DMA mask configuration API
Date: Fri, 25 Mar 2016 12:39:12 +0800	[thread overview]
Message-ID: <201603251224.amlQiwhC%fengguang.wu@intel.com> (raw)
In-Reply-To: <20160325040234.GA6185@peterchendt>

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

Hi Peter,

[auto build test ERROR on v4.5-rc7]
[also build test ERROR on next-20160324]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]

url:    https://github.com/0day-ci/linux/commits/Peter-Chen/usb-chipidea-add-DMA-mask-configuration-API/20160325-120535
config: i386-randconfig-s1-201612 (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

>> ERROR: "ci_hdrc_set_dma_mask" [drivers/usb/chipidea/ci_hdrc_msm.ko] undefined!

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 23634 bytes --]

  reply	other threads:[~2016-03-25  4:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22  5:32 [PATCH] usb: chipidea: Configure DMA properties and ops from DT Bjorn Andersson
2016-02-22  6:02 ` Peter Chen
2016-02-22  6:14   ` Bjorn Andersson
2016-02-22 10:03 ` Srinivas Kandagatla
2016-02-22 22:07   ` Bjorn Andersson
2016-02-23  1:31     ` Peter Chen
2016-03-02 22:59     ` Li Yang
2016-03-08 19:52       ` Li Yang
2016-03-09  3:40         ` Bjorn Andersson
2016-03-09 23:16           ` Li Yang
2016-03-14 10:51             ` Peter Chen
2016-03-17 15:52               ` Arnd Bergmann
2016-03-18  1:54                 ` Peter Chen
2016-03-18  3:25                   ` Rajesh Bhagat
2016-03-18  7:28                   ` Arnd Bergmann
2016-03-18 10:56                   ` Russell King - ARM Linux
2016-03-25  4:02           ` Peter Chen
2016-03-25  4:39             ` kbuild test robot [this message]
2016-10-21 16:59 ` [RESEND PATCH] " Bjorn Andersson
2016-10-21 17:38   ` Stephen Boyd
2016-10-21 17:53     ` Bjorn Andersson
2016-10-22  6:22     ` Sriram Dash

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=201603251224.amlQiwhC%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=Peter.Chen@nxp.com \
    --cc=arnd@arndb.de \
    --cc=bjorn.andersson@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hzpeterchen@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=leoli@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=rajesh.bhagat@nxp.com \
    --cc=srinivas.kandagatla@linaro.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;
as well as URLs for NNTP newsgroup(s).