From: kbuild test robot <lkp@intel.com>
To: Arushi Singhal <arushisinghal19971997@gmail.com>
Cc: kbuild-all@01.org, jic23@kernel.org, devel@driverdev.osuosl.org,
Lars-Peter Clausen <lars@metafoo.de>,
linux-iio@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, outreachy-kernel@googlegroups.com,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Hartmut Knaack <knaack.h@gmx.de>
Subject: Re: [PATCH] staging: tsl2x7x: Moved contents of the header to the source file.
Date: Sat, 25 Mar 2017 16:10:22 +0800 [thread overview]
Message-ID: <201703251634.MshWRfXM%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170323115357.GA24360@arushi-HP-Pavilion-Notebook>
[-- Attachment #1: Type: text/plain, Size: 2161 bytes --]
Hi Arushi,
[auto build test ERROR on iio/togreg]
[also build test ERROR on v4.11-rc3 next-20170324]
[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/Arushi-Singhal/staging-tsl2x7x-Moved-contents-of-the-header-to-the-source-file/20170325-152616
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
config: x86_64-randconfig-x004-201712 (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=x86_64
All errors (new ones prefixed by >>):
In file included from drivers/staging/iio/light/tsl2x7x_core.c:33:0:
>> drivers/staging/iio/light/tsl2x7x.h:39:40: error: 'TSL2X7X_MAX_LUX_TABLE_SIZE' undeclared here (not in a function)
struct tsl2x7x_lux platform_lux_table[TSL2X7X_MAX_LUX_TABLE_SIZE];
^~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/TSL2X7X_MAX_LUX_TABLE_SIZE +39 drivers/staging/iio/light/tsl2x7x.h
3c97c08b Jon Brenner 2012-04-24 33 *
3c97c08b Jon Brenner 2012-04-24 34 */
3c97c08b Jon Brenner 2012-04-24 35 struct tsl2X7X_platform_data {
3c97c08b Jon Brenner 2012-04-24 36 int (*platform_power)(struct device *dev, pm_message_t);
3c97c08b Jon Brenner 2012-04-24 37 int (*power_on)(struct iio_dev *indio_dev);
3c97c08b Jon Brenner 2012-04-24 38 int (*power_off)(struct i2c_client *dev);
3c97c08b Jon Brenner 2012-04-24 @39 struct tsl2x7x_lux platform_lux_table[TSL2X7X_MAX_LUX_TABLE_SIZE];
3c97c08b Jon Brenner 2012-04-24 40 struct tsl2x7x_settings *platform_default_settings;
3c97c08b Jon Brenner 2012-04-24 41 };
3c97c08b Jon Brenner 2012-04-24 42
:::::: The code at line 39 was first introduced by commit
:::::: 3c97c08b5735ac05ebc0cbd0aa7722393f50b846 staging: iio: add TAOS tsl2x7x driver
:::::: TO: Jon Brenner <jbrenner@taosinc.com>
:::::: CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
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: 26691 bytes --]
prev parent reply other threads:[~2017-03-25 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 11:53 Arushi Singhal
2017-03-23 11:59 ` Lars-Peter Clausen
2017-03-25 8:10 ` 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=201703251634.MshWRfXM%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=arushisinghal19971997@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=kbuild-all@01.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=pmeerw@pmeerw.net \
/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®