From: kbuild test robot <lkp@intel.com>
To: Amit Ghadge <amitg.b14@gmail.com>
Cc: kbuild-all@01.org, abbotti@mev.co.uk, devel@driverdev.osuosl.org,
gregkh@linuxfoundation.org, Amit Ghadge <amitg.b14@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Staging: comedi: ni_670x.c: Fix warnings and check.
Date: Sun, 4 Sep 2016 04:42:50 +0800 [thread overview]
Message-ID: <201609040417.j6Ufd76B%fengguang.wu@intel.com> (raw)
In-Reply-To: <1472933463-5290-2-git-send-email-amitg.b14@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1960 bytes --]
Hi Amit,
[auto build test ERROR on v4.8-rc4]
[cannot apply to staging/staging-testing next-20160825]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]
url: https://github.com/0day-ci/linux/commits/Amit-Ghadge/Staging-comedi-ni_daq_dio24-c-Fix-block-comments-use-on-subsequent-lines/20160904-041301
config: xtensa-allmodconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=xtensa
All errors (new ones prefixed by >>):
drivers/staging/comedi/drivers/ni_670x.c: In function 'ni_670x_auto_attach':
>> drivers/staging/comedi/drivers/ni_670x.c:223:32: error: 'range_0_20ma' undeclared (first use in this function)
range_table_list[16 + i] = &range_0_20ma;
^
drivers/staging/comedi/drivers/ni_670x.c:223:32: note: each undeclared identifier is reported only once for each function it appears in
vim +/range_0_20ma +223 drivers/staging/comedi/drivers/ni_670x.c
217 GFP_KERNEL);
218 if (!range_table_list)
219 return -ENOMEM;
220 s->range_table_list = range_table_list;
221 for (i = 0; i < 16; i++) {
222 range_table_list[i] = &range_bipolar10;
> 223 range_table_list[16 + i] = &range_0_20ma;
224 }
225 } else {
226 s->range_table = &range_bipolar10;
---
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: 46035 bytes --]
next prev parent reply other threads:[~2016-09-03 20:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 20:11 [PATCH 1/2] Staging: comedi: ni_daq_dio24.c: Fix block comments use * on subsequent lines Amit Ghadge
2016-09-03 20:11 ` [PATCH 2/2] Staging: comedi: ni_670x.c: Fix warnings and check Amit Ghadge
2016-09-03 20:42 ` kbuild test robot [this message]
2016-09-04 8:35 ` Greg KH
2016-09-04 10:15 ` Amit Ghadge
2016-09-05 13:11 ` Ian Abbott
2016-09-05 13:32 ` Ian Abbott
2016-09-05 14:12 ` Amit Ghadge
2016-09-05 13:15 ` [PATCH 1/2] Staging: comedi: ni_daq_dio24.c: Fix block comments use * on subsequent lines Ian Abbott
2016-09-05 14:13 ` Amit Ghadge
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=201609040417.j6Ufd76B%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=abbotti@mev.co.uk \
--cc=amitg.b14@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.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®