mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: simran singhal <singhalsimran0@gmail.com>
Cc: kbuild-all@01.org, lars@metafoo.de, devel@driverdev.osuosl.org,
	Michael.Hennerich@analog.com, linux-iio@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, outreachy-kernel@googlegroups.com,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Hartmut Knaack <knaack.h@gmx.de>,
	jic23@kernel.org
Subject: Re: [PATCH v7] staging: adis16060_core: Replace mlock with buf_lock and refactor code
Date: Thu, 23 Mar 2017 04:00:53 +0800	[thread overview]
Message-ID: <201703230313.COe3PSCe%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170320125320.GA22516@singhal-Inspiron-5558>

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

Hi simran,

[auto build test WARNING on iio/togreg]
[also build test WARNING on v4.11-rc3 next-20170322]
[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/simran-singhal/staging-adis16060_core-Replace-mlock-with-buf_lock-and-refactor-code/20170323-031726
base:   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
config: x86_64-randconfig-s0-03230201 (attached as .config)
compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All warnings (new ones prefixed by >>):

   drivers/staging/iio/gyro/adis16060_core.c: In function 'adis16060_read_raw':
>> drivers/staging/iio/gyro/adis16060_core.c:79: warning: unused variable 'st'

vim +/st +79 drivers/staging/iio/gyro/adis16060_core.c

    63		if (!ret)
    64			*val = ((st->buf[0] & 0x3) << 12) |
    65				 (st->buf[1] << 4) |
    66				 ((st->buf[2] >> 4) & 0xF);
    67		mutex_unlock(&st->buf_lock);
    68	
    69		return ret;
    70	}
    71	
    72	static int adis16060_read_raw(struct iio_dev *indio_dev,
    73				      struct iio_chan_spec const *chan,
    74				      int *val, int *val2,
    75				      long mask)
    76	{
    77		u16 tval = 0;
    78		int ret;
  > 79		struct adis16060_state *st = iio_priv(indio_dev);
    80	
    81		switch (mask) {
    82		case IIO_CHAN_INFO_RAW:
    83			ret = adis16060_spi_write_than_read(indio_dev,
    84							    chan->address, &tval);
    85			if (ret < 0)
    86				return ret;
    87	

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

  parent reply	other threads:[~2017-03-22 20:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 12:53 simran singhal
2017-03-21 19:40 ` Jonathan Cameron
2017-03-22 20:00 ` kbuild test robot [this message]
2017-03-22 20:14   ` Jonathan Cameron

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=201703230313.COe3PSCe%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=kbuild-all@01.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=pmeerw@pmeerw.net \
    --cc=singhalsimran0@gmail.com \
    /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®