From: kbuild test robot <lkp@intel.com>
To: "Andrew F. Davis" <afd@ti.com>
Cc: kbuild-all@01.org, Russell King <linux@armlinux.org.uk>,
Miguel Ojeda Sandonis <miguel.ojeda.sandonis@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Sebastian Reichel <sre@kernel.org>,
Wolfram Sang <wsa@the-dreams.de>,
Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <j.anaszewski@samsung.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Lauro Ramos Venancio <lauro.venancio@openbossa.org>,
Aloisio Almeida Jr <aloisio.almeida@openbossa.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>,
linux-pwm@vger.kernel.org, lguest@lists.ozlabs.org,
linux-wireless@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, "Andrew F . Davis" <afd@ti.com>,
linux-gpio@vger.kernel.org, linux-i2c@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-leds@vger.kernel.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH 11/12] mmc: Only descend into mmc directory when CONFIG_MMC is set
Date: Tue, 14 Jun 2016 09:33:20 +0800 [thread overview]
Message-ID: <201606140907.a7yCPk00%fengguang.wu@intel.com> (raw)
In-Reply-To: <20160613200211.14790-12-afd@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
Hi,
[auto build test ERROR on gpio/for-next]
[also build test ERROR on v4.7-rc3 next-20160609]
[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/Andrew-F-Davis/gpio-Only-descend-into-gpio-directory-when-CONFIG_GPIOLIB-is-set/20160614-061705
base: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git for-next
config: i386-randconfig-sb0-06140627 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> ERROR: "sdhci_pci_get_data" [drivers/mmc/host/sdhci-pci.ko] undefined!
>> ERROR: "sdhci_pci_spt_drive_strength" [drivers/mmc/host/sdhci-pci.ko] undefined!
ERROR: "hsi_board_list" [drivers/hsi/hsi.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: 24709 bytes --]
parent reply other threads:[~2016-06-14 1:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20160613200211.14790-12-afd@ti.com>]
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=201606140907.a7yCPk00%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=afd@ti.com \
--cc=aloisio.almeida@openbossa.org \
--cc=benh@kernel.crashing.org \
--cc=j.anaszewski@samsung.com \
--cc=kbuild-all@01.org \
--cc=lauro.venancio@openbossa.org \
--cc=lguest@lists.ozlabs.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mchehab@osg.samsung.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mingo@kernel.org \
--cc=rpurdie@rpsys.net \
--cc=rusty@rustcorp.com.au \
--cc=sameo@linux.intel.com \
--cc=sre@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=wsa@the-dreams.de \
/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®