mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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:29:18 +0800	[thread overview]
Message-ID: <201609041904.S6ER4Q18%fengguang.wu@intel.com> (raw)
In-Reply-To: <1472979624-25219-1-git-send-email-amitg.b14@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3831 bytes --]

Hi Amit,

[auto build test WARNING 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-randconfig-i0-201636 (attached as .config)
compiler: gcc-4.8 (Debian 4.8.4-1) 4.8.4
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All warnings (new ones prefixed by >>):

   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: warning: missing braces around initializer [-Wmissing-braces]
   drivers/staging/comedi/drivers/adv_pci1724.c:76:3: warning: (near initialization for 'adv_pci1724_ao_ranges.range[1]') [-Wmissing-braces]
   drivers/staging/comedi/drivers/adv_pci1724.c:76:3: error: initializer element is not constant
   drivers/staging/comedi/drivers/adv_pci1724.c:76:3: error: (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: error: (near initialization for 'adv_pci1724_ao_ranges.range[1].max')
   drivers/staging/comedi/drivers/adv_pci1724.c:78:3: warning: braces around scalar initializer [enabled by default]
      RANGE_unitless(0, 1)
      ^
   drivers/staging/comedi/drivers/adv_pci1724.c:78:3: warning: (near initialization for 'adv_pci1724_ao_ranges.range[1].flags') [enabled by default]
>> drivers/staging/comedi/drivers/adv_pci1724.c:78:3: warning: excess elements in scalar initializer [enabled by default]
   drivers/staging/comedi/drivers/adv_pci1724.c:78:3: warning: (near initialization for 'adv_pci1724_ao_ranges.range[1].flags') [enabled by default]
>> drivers/staging/comedi/drivers/adv_pci1724.c:78:3: warning: excess elements in scalar initializer [enabled by default]
   drivers/staging/comedi/drivers/adv_pci1724.c:78:3: warning: (near initialization for 'adv_pci1724_ao_ranges.range[1].flags') [enabled by default]
   cc1: some warnings being treated as errors

vim +78 drivers/staging/comedi/drivers/adv_pci1724.c

c2edc021 H Hartley Sweeten 2014-11-20  70  #define PCI1724_BOARD_ID_REG		0x10
70adf763 H Hartley Sweeten 2014-11-20  71  #define PCI1724_BOARD_ID_MASK		(0xf << 0)
f165d815 Frank Mori Hess   2013-03-12  72  
474bfe5f H Hartley Sweeten 2014-11-20  73  static const struct comedi_lrange adv_pci1724_ao_ranges = {
348dc03e H Hartley Sweeten 2013-12-09  74  	4, {
f165d815 Frank Mori Hess   2013-03-12  75  		BIP_RANGE(10),
f165d815 Frank Mori Hess   2013-03-12 @76  		RANGE_mA(0, 20),
f165d815 Frank Mori Hess   2013-03-12  77  		RANGE_mA(4, 20),
f165d815 Frank Mori Hess   2013-03-12 @78  		RANGE_unitless(0, 1)
f165d815 Frank Mori Hess   2013-03-12  79  	}
f165d815 Frank Mori Hess   2013-03-12  80  };
f165d815 Frank Mori Hess   2013-03-12  81  

:::::: The code at line 78 was first introduced by commit
:::::: f165d815d50f158be43aa12c5c800fd27bbecad3 staging: comedi: adv_pci1724: new driver

:::::: TO: Frank Mori Hess <fmh6jj@gmail.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: 30544 bytes --]

  parent reply	other threads:[~2016-09-04 11:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-04  9:00 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 [this message]
2016-09-04 11:49 ` kbuild test robot
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=201609041904.S6ER4Q18%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®