From: kbuild test robot <lkp@intel.com>
To: Randy Li <ayaka@soulik.info>
Cc: kbuild-all@01.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, lgirdwood@gmail.com,
broonie@kernel.org, perex@perex.cz, tiwai@suse.com,
john@metanate.com, Randy Li <ayaka@soulik.info>
Subject: Re: [PATCH] ASoC: es8328: explict I2C and SPI menu entry
Date: Mon, 15 Aug 2016 01:26:12 +0800 [thread overview]
Message-ID: <201608150149.5VML9DZk%fengguang.wu@intel.com> (raw)
In-Reply-To: <1471163629-11193-1-git-send-email-ayaka@soulik.info>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
Hi Randy,
[auto build test ERROR on asoc/for-next]
[also build test ERROR on v4.8-rc1 next-20160812]
[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/Randy-Li/ASoC-es8328-explict-I2C-and-SPI-menu-entry/20160814-163615
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
config: x86_64-randconfig-x018-08142330 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
sound/built-in.o: In function `es8328_spi_probe':
>> es8328-spi.c:(.text+0x706ba): undefined reference to `__devm_regmap_init_spi'
sound/built-in.o: In function `es8328_spi_driver_init':
>> es8328-spi.c:(.init.text+0x3e3b): undefined reference to `__spi_register_driver'
---
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: 25769 bytes --]
prev parent reply other threads:[~2016-08-14 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-14 8:33 Randy Li
2016-08-14 15:10 ` kbuild test robot
2016-08-14 17:26 ` 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=201608150149.5VML9DZk%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=ayaka@soulik.info \
--cc=broonie@kernel.org \
--cc=john@metanate.com \
--cc=kbuild-all@01.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®