From: kbuild test robot <lkp@intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: kbuild-all@01.org, Lee Jones <lee.jones@linaro.org>,
Hans de Goede <hdegoede@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] mfd: axp20c-i2c: Select designware i2c-bus driver on x86
Date: Thu, 30 Mar 2017 13:21:24 +0800 [thread overview]
Message-ID: <201703301308.7OQ2qooH%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170329185751.25389-2-hdegoede@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
Hi Hans,
[auto build test WARNING on ljones-mfd/for-mfd-next]
[also build test WARNING on v4.11-rc4 next-20170329]
[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/Hans-de-Goede/mfd-intel_soc_pmic-Select-designware-i2c-bus-driver/20170330-102517
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
config: i386-randconfig-x074-201713 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
warning: (MFD_AXP20X_I2C) selects I2C_DESIGNWARE_BAYTRAIL which has unmet direct dependencies (I2C && HAS_IOMEM && ACPI && (I2C_DESIGNWARE_PLATFORM=m && IOSF_MBI || I2C_DESIGNWARE_PLATFORM=y && IOSF_MBI=y))
---
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: 21061 bytes --]
next prev parent reply other threads:[~2017-03-30 5:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 18:57 [PATCH v2 1/2] mfd: intel_soc_pmic: Select designware i2c-bus driver Hans de Goede
2017-03-29 18:57 ` [PATCH v2 2/2] mfd: axp20c-i2c: Select designware i2c-bus driver on x86 Hans de Goede
2017-03-30 5:21 ` kbuild test robot
2017-03-30 5:21 ` kbuild test robot [this message]
2017-04-03 10:27 ` Lee Jones
2017-04-03 10:48 ` Hans de Goede
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=201703301308.7OQ2qooH%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=hdegoede@redhat.com \
--cc=kbuild-all@01.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@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®