Re: [PATCH 2/2] Staging: comedi: ni_670x.c: Fix warnings and check.

From: kbuild test robot
Date: Sat Sep 03 2016 - 16:44:03 EST


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: .config.gz
Description: Binary data