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] Staging: comedi: ni_daq_dio24.c: Fix block comments use * on subsequent lines.
Date: Sun, 4 Sep 2016 19:49:04 +0800 [thread overview]
Message-ID: <201609041900.E4RVUIB2%fengguang.wu@intel.com> (raw)
In-Reply-To: <1472979624-25219-1-git-send-email-amitg.b14@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 11536 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-170303
config: i386-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All error/warnings (new ones prefixed by >>):
>> drivers/staging/comedi/range.c:35:49: error: implicit declaration of function 'RANGE_mA' [-Werror=implicit-function-declaration]
const struct comedi_lrange range_0_20mA = { 1, {RANGE_mA(0, 20)} };
^~~~~~~~
>> drivers/staging/comedi/range.c:35:49: error: initializer element is not constant
drivers/staging/comedi/range.c:35:49: note: (near initialization for 'range_0_20mA.range[0].min')
drivers/staging/comedi/range.c:37:49: error: initializer element is not constant
const struct comedi_lrange range_4_20mA = { 1, {RANGE_mA(4, 20)} };
^~~~~~~~
drivers/staging/comedi/range.c:37:49: note: (near initialization for 'range_4_20mA.range[0].min')
drivers/staging/comedi/range.c:39:49: error: initializer element is not constant
const struct comedi_lrange range_0_32mA = { 1, {RANGE_mA(0, 32)} };
^~~~~~~~
drivers/staging/comedi/range.c:39:49: note: (near initialization for 'range_0_32mA.range[0].min')
cc1: some warnings being treated as errors
--
>> drivers/staging/comedi/drivers/pcl726.c:82:3: error: 'range_4_20mA' undeclared here (not in a function)
&range_4_20mA,
^~~~~~~~~~~~
>> drivers/staging/comedi/drivers/pcl726.c:90:2: error: initializer element is not constant
&range_4_20mA
^
drivers/staging/comedi/drivers/pcl726.c:90:2: note: (near initialization for 'rangelist_727[3]')
drivers/staging/comedi/drivers/pcl726.c:98:2: error: initializer element is not constant
&range_4_20mA,
^
drivers/staging/comedi/drivers/pcl726.c:98:2: note: (near initialization for 'rangelist_728[4]')
>> drivers/staging/comedi/drivers/pcl726.c:99:3: error: 'range_0_20mA' undeclared here (not in a function)
&range_0_20mA
^~~~~~~~~~~~
drivers/staging/comedi/drivers/pcl726.c:99:2: error: initializer element is not constant
&range_0_20mA
^
drivers/staging/comedi/drivers/pcl726.c:99:2: note: (near initialization for 'rangelist_728[5]')
--
>> drivers/staging/comedi/drivers/dac02.c:66:3: error: implicit declaration of function 'RANGE_mA' [-Werror=implicit-function-declaration]
RANGE_mA(4, 20),
^~~~~~~~
>> drivers/staging/comedi/drivers/dac02.c:66:3: error: initializer element is not constant
drivers/staging/comedi/drivers/dac02.c:66:3: note: (near initialization for 'das02_ao_ranges.range[4].min')
>> drivers/staging/comedi/drivers/dac02.c:67:3: warning: braces around scalar initializer
RANGE_ext(0, 1)
^~~~~~~~~
drivers/staging/comedi/drivers/dac02.c:67:3: note: (near initialization for 'das02_ao_ranges.range[4].max')
In file included from drivers/staging/comedi/drivers/dac02.c:38:0:
>> drivers/staging/comedi/drivers/../comedidev.h:584:38: warning: excess elements in scalar initializer
#define RANGE_ext(a, b) {(a) * 1e6, (b) * 1e6, RF_EXTERNAL}
^
>> drivers/staging/comedi/drivers/dac02.c:67:3: note: in expansion of macro 'RANGE_ext'
RANGE_ext(0, 1)
^~~~~~~~~
drivers/staging/comedi/drivers/../comedidev.h:584:38: note: (near initialization for 'das02_ao_ranges.range[4].max')
#define RANGE_ext(a, b) {(a) * 1e6, (b) * 1e6, RF_EXTERNAL}
^
>> drivers/staging/comedi/drivers/dac02.c:67:3: note: in expansion of macro 'RANGE_ext'
RANGE_ext(0, 1)
^~~~~~~~~
In file included from drivers/staging/comedi/drivers/../comedidev.h:28:0,
from drivers/staging/comedi/drivers/dac02.c:38:
>> drivers/staging/comedi/drivers/../comedi.h:897:22: warning: excess elements in scalar initializer
#define RF_EXTERNAL 0x100
^
>> drivers/staging/comedi/drivers/../comedidev.h:584:49: note: in expansion of macro 'RF_EXTERNAL'
#define RANGE_ext(a, b) {(a) * 1e6, (b) * 1e6, RF_EXTERNAL}
^~~~~~~~~~~
>> drivers/staging/comedi/drivers/dac02.c:67:3: note: in expansion of macro 'RANGE_ext'
RANGE_ext(0, 1)
^~~~~~~~~
drivers/staging/comedi/drivers/../comedi.h:897:22: note: (near initialization for 'das02_ao_ranges.range[4].max')
#define RF_EXTERNAL 0x100
^
>> drivers/staging/comedi/drivers/../comedidev.h:584:49: note: in expansion of macro 'RF_EXTERNAL'
#define RANGE_ext(a, b) {(a) * 1e6, (b) * 1e6, RF_EXTERNAL}
^~~~~~~~~~~
>> drivers/staging/comedi/drivers/dac02.c:67:3: note: in expansion of macro 'RANGE_ext'
RANGE_ext(0, 1)
^~~~~~~~~
>> drivers/staging/comedi/drivers/dac02.c:61:5: warning: missing braces around initializer [-Wmissing-braces]
6, {
^
drivers/staging/comedi/drivers/dac02.c:61:5: note: (near initialization for 'das02_ao_ranges.range')
drivers/staging/comedi/drivers/dac02.c:60:53: warning: missing braces around initializer [-Wmissing-braces]
static const struct comedi_lrange das02_ao_ranges = {
^
drivers/staging/comedi/drivers/dac02.c:60:53: note: (near initialization for 'das02_ao_ranges')
cc1: some warnings being treated as errors
--
drivers/staging/comedi/drivers/dt2815.c: In function 'dt2815_attach':
>> drivers/staging/comedi/drivers/dt2815.c:177:9: error: 'range_4_20mA' undeclared (first use in this function)
? &range_4_20mA : &range_0_32mA;
^~~~~~~~~~~~
drivers/staging/comedi/drivers/dt2815.c:177:9: note: each undeclared identifier is reported only once for each function it appears in
>> drivers/staging/comedi/drivers/dt2815.c:177:25: error: 'range_0_32mA' undeclared (first use in this function)
? &range_4_20mA : &range_0_32mA;
^~~~~~~~~~~~
--
>> drivers/staging/comedi/drivers/adv_pci1724.c:76:3: error: implicit declaration of function 'RANGE_mA' [-Werror=implicit-function-declaration]
RANGE_mA(0, 20),
^~~~~~~~
>> drivers/staging/comedi/drivers/adv_pci1724.c:76:3: error: initializer element is not constant
drivers/staging/comedi/drivers/adv_pci1724.c:76:3: note: (near initialization for 'adv_pci1724_ao_ranges.range[1].min')
drivers/staging/comedi/drivers/adv_pci1724.c:77:3: error: initializer element is not constant
RANGE_mA(4, 20),
^~~~~~~~
drivers/staging/comedi/drivers/adv_pci1724.c:77:3: note: (near initialization for 'adv_pci1724_ao_ranges.range[1].max')
>> drivers/staging/comedi/drivers/adv_pci1724.c:78:3: warning: braces around scalar initializer
RANGE_unitless(0, 1)
^~~~~~~~~~~~~~
drivers/staging/comedi/drivers/adv_pci1724.c:78:3: note: (near initialization for 'adv_pci1724_ao_ranges.range[1].flags')
In file included from drivers/staging/comedi/drivers/../comedi_pci.h:24:0,
from drivers/staging/comedi/drivers/adv_pci1724.c:51:
drivers/staging/comedi/drivers/../comedidev.h:586:42: warning: excess elements in scalar initializer
#define RANGE_unitless(a, b) {(a) * 1e6, (b) * 1e6, 0}
^
>> drivers/staging/comedi/drivers/adv_pci1724.c:78:3: note: in expansion of macro 'RANGE_unitless'
RANGE_unitless(0, 1)
^~~~~~~~~~~~~~
drivers/staging/comedi/drivers/../comedidev.h:586:42: note: (near initialization for 'adv_pci1724_ao_ranges.range[1].flags')
#define RANGE_unitless(a, b) {(a) * 1e6, (b) * 1e6, 0}
^
>> drivers/staging/comedi/drivers/adv_pci1724.c:78:3: note: in expansion of macro 'RANGE_unitless'
RANGE_unitless(0, 1)
^~~~~~~~~~~~~~
drivers/staging/comedi/drivers/../comedidev.h:586:53: warning: excess elements in scalar initializer
#define RANGE_unitless(a, b) {(a) * 1e6, (b) * 1e6, 0}
^
>> drivers/staging/comedi/drivers/adv_pci1724.c:78:3: note: in expansion of macro 'RANGE_unitless'
RANGE_unitless(0, 1)
^~~~~~~~~~~~~~
drivers/staging/comedi/drivers/../comedidev.h:586:53: note: (near initialization for 'adv_pci1724_ao_ranges.range[1].flags')
#define RANGE_unitless(a, b) {(a) * 1e6, (b) * 1e6, 0}
^
>> drivers/staging/comedi/drivers/adv_pci1724.c:78:3: note: in expansion of macro 'RANGE_unitless'
RANGE_unitless(0, 1)
^~~~~~~~~~~~~~
>> drivers/staging/comedi/drivers/adv_pci1724.c:73:59: warning: missing braces around initializer [-Wmissing-braces]
static const struct comedi_lrange adv_pci1724_ao_ranges = {
^
drivers/staging/comedi/drivers/adv_pci1724.c:73:59: note: (near initialization for 'adv_pci1724_ao_ranges')
cc1: some warnings being treated as errors
--
drivers/staging/comedi/drivers/ni_670x.c: In function 'ni_670x_auto_attach':
>> drivers/staging/comedi/drivers/ni_670x.c:225: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:225:32: note: each undeclared identifier is reported only once for each function it appears in
vim +/RANGE_mA +35 drivers/staging/comedi/range.c
f0f29184 Mark Rankilor 2010-05-03 29 const struct comedi_lrange range_unipolar10 = { 1, {UNI_RANGE(10)} };
5660e742 H Hartley Sweeten 2013-04-12 30 EXPORT_SYMBOL_GPL(range_unipolar10);
f0f29184 Mark Rankilor 2010-05-03 31 const struct comedi_lrange range_unipolar5 = { 1, {UNI_RANGE(5)} };
5660e742 H Hartley Sweeten 2013-04-12 32 EXPORT_SYMBOL_GPL(range_unipolar5);
5f8eb72c H Hartley Sweeten 2013-04-03 33 const struct comedi_lrange range_unipolar2_5 = { 1, {UNI_RANGE(2.5)} };
5660e742 H Hartley Sweeten 2013-04-12 34 EXPORT_SYMBOL_GPL(range_unipolar2_5);
2c71c4ff H Hartley Sweeten 2013-04-03 @35 const struct comedi_lrange range_0_20mA = { 1, {RANGE_mA(0, 20)} };
5660e742 H Hartley Sweeten 2013-04-12 36 EXPORT_SYMBOL_GPL(range_0_20mA);
2c71c4ff H Hartley Sweeten 2013-04-03 37 const struct comedi_lrange range_4_20mA = { 1, {RANGE_mA(4, 20)} };
5660e742 H Hartley Sweeten 2013-04-12 38 EXPORT_SYMBOL_GPL(range_4_20mA);
:::::: The code at line 35 was first introduced by commit
:::::: 2c71c4ff57a6564097bedd45bc589f73da798a3a staging: comedi: range: introduce some simple mA ranges
:::::: TO: H Hartley Sweeten <hsweeten@visionengravers.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/octet-stream, Size: 55851 bytes --]
next prev parent reply other threads:[~2016-09-04 12:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 9:00 [PATCH] Staging: comedi: ni_daq_dio24.c: Fix block comments use * on subsequent lines Amit Ghadge
2016-09-04 9:02 ` Amit Ghadge
2016-09-04 11:08 ` kbuild test robot
2016-09-04 11:29 ` kbuild test robot
2016-09-04 11:49 ` kbuild test robot [this message]
2016-09-04 12:22 ` Amit Ghadge
2016-09-04 22:31 ` kbuild test robot
-- strict thread matches above, loose matches on Subject: below --
2016-09-04 9:08 Amit Ghadge
2016-09-04 9:42 ` Giedrius Statkevičius
2016-09-04 9:58 ` Amit Ghadge
2016-09-03 19:25 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=201609041900.E4RVUIB2%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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.