mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: devendra sharma <devendra.sharma9091@gmail.com>
Cc: kbuild-all@01.org, abbotti@mev.co.uk, devel@driverdev.osuosl.org,
	ansonjacob.aj@gmail.com, gregkh@linuxfoundation.org,
	devendra sharma <devendra.sharma9091@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: comedi: cb_pcidas64: Fixed coding issue about multiple line dereferencing
Date: Tue, 20 Dec 2016 02:40:16 +0800	[thread overview]
Message-ID: <201612200224.S6DAQ2c3%fengguang.wu@intel.com> (raw)
In-Reply-To: <1482160468-5614-1-git-send-email-devendra.sharma9091@gmail.com>

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

Hi devendra,

[auto build test WARNING on staging/staging-testing]
[also build test WARNING on v4.9 next-20161219]
[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/devendra-sharma/staging-comedi-cb_pcidas64-Fixed-coding-issue-about-multiple-line-dereferencing/20161220-020116
config: x86_64-randconfig-x017-201651 (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 warnings (new ones prefixed by >>):

   drivers/staging/comedi/drivers/cb_pcidas64.c: In function 'setup_channel_queue':
>> drivers/staging/comedi/drivers/cb_pcidas64.c:2478:5: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
        unsigned int ch = cmd->chanlist[i];
        ^~~~~~~~

vim +2478 drivers/staging/comedi/drivers/cb_pcidas64.c

  2462				/* use external queue */
  2463				if (dev->write_subdev && dev->write_subdev->busy) {
  2464					warn_external_queue(dev);
  2465					return -EBUSY;
  2466				}
  2467				devpriv->hw_config_bits |= EXT_QUEUE_BIT;
  2468				writew(devpriv->hw_config_bits,
  2469				       devpriv->main_iobase + HW_CONFIG_REG);
  2470				/* clear DAC buffer to prevent weird interactions */
  2471				writew(0,
  2472				       devpriv->main_iobase + DAC_BUFFER_CLEAR_REG);
  2473				/* clear queue pointer */
  2474				writew(0, devpriv->main_iobase + ADC_QUEUE_CLEAR_REG);
  2475				/* load external queue */
  2476				for (i = 0; i < cmd->chanlist_len; i++) {
  2477					bits = 0;
> 2478					unsigned int ch = cmd->chanlist[i];
  2479					/* set channel */
  2480					bits |= adc_chan_bits(CR_CHAN(ch));
  2481					/* set gain */
  2482					bits |= ai_range_bits_6xxx(dev,
  2483								   CR_RANGE(ch));
  2484					/* set single-ended / differential */
  2485					bits |= se_diff_bit_6xxx(dev,
  2486								 CR_AREF(ch) ==

---
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: 28854 bytes --]

  parent reply	other threads:[~2016-12-19 18:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-19 15:14 devendra sharma
2016-12-19 18:12 ` Ian Abbott
2016-12-19 18:40 ` kbuild test robot [this message]
2017-01-03 14:26 ` Greg KH

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=201612200224.S6DAQ2c3%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=abbotti@mev.co.uk \
    --cc=ansonjacob.aj@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=devendra.sharma9091@gmail.com \
    --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

Powered by JetHome