From: kbuild test robot <lkp@intel.com>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org, Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Gwendal Grignou <gwendal@chromium.org>,
Guenter Roeck <groeck@chromium.org>
Subject: Re: [PATCH] iio: cros_ec_light_prox: add ChromeOS EC Light and Proximity Sensors
Date: Sat, 26 Nov 2016 16:35:44 +0800 [thread overview]
Message-ID: <201611261638.XSABa9rA%fengguang.wu@intel.com> (raw)
In-Reply-To: <1480075385-26091-1-git-send-email-enric.balletbo@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 974 bytes --]
Hi Gwendal,
[auto build test WARNING on iio/togreg]
[also build test WARNING on next-20161125]
[cannot apply to v4.9-rc6]
[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/Enric-Balletbo-i-Serra/iio-cros_ec_light_prox-add-ChromeOS-EC-Light-and-Proximity-Sensors/20161125-232924
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
config: um-allmodconfig (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=um
All warnings (new ones prefixed by >>):
warning: (IIO_CROS_EC_LIGHT_PROX) selects IIO_CROS_EC_SENSORS_CORE which has unmet direct dependencies (IIO && SYSFS && MFD_CROS_EC)
---
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: 18718 bytes --]
next prev parent reply other threads:[~2016-11-26 8:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 12:03 Enric Balletbo i Serra
2016-11-26 8:35 ` kbuild test robot [this message]
2016-11-27 10:39 ` Jonathan Cameron
2016-11-30 8:57 ` Enric Balletbo Serra
2016-12-03 9:54 ` Jonathan Cameron
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=201611261638.XSABa9rA%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=jic23@kernel.org \
--cc=kbuild-all@01.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.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
Powered by JetHome