mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Parthiban Nallathambi <pn@denx.de>
Cc: kbuild-all@01.org, jic23@kernel.org, knaack.h@gmx.de,
	lars@metafoo.de, pmeerw@pmeerw.net, robh+dt@kernel.org,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	mark.rutland@arm.com, devicetree@vger.kernel.org,
	matthias.bgg@gmail.com, wd@denx.de, sbabic@denx.de, hs@denx.de,
	Parthiban Nallathambi <pn@denx.de>
Subject: Re: [PATCH 1/2] iio: light: Add support for vishay vcnl4035
Date: Thu, 28 Jun 2018 23:35:49 +0800	[thread overview]
Message-ID: <201806282346.z3EjCFvh%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180628123021.1628338-1-pn@denx.de>

Hi Parthiban,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on iio/togreg]
[also build test WARNING on v4.18-rc2 next-20180628]
[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/Parthiban-Nallathambi/iio-light-Add-support-for-vishay-vcnl4035/20180628-213034
base:   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
reproduce:
        # apt-get install sparse
        make ARCH=x86_64 allmodconfig
        make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> drivers/iio/light/vcnl4035.c:136:28: sparse: cast to restricted __le16

vim +136 drivers/iio/light/vcnl4035.c

   115	
   116	static irqreturn_t vcnl4035_trigger_consumer_handler(int irq, void *p)
   117	{
   118		struct iio_poll_func *pf = p;
   119		struct iio_dev *indio_dev = pf->indio_dev;
   120		struct vcnl4035_data *data = iio_priv(indio_dev);
   121		int als_data;
   122		int ret;
   123	
   124		if (iio_trigger_using_own(indio_dev) && data->irq_timestamp) {
   125			pf->timestamp = data->irq_timestamp;
   126			data->irq_timestamp = 0;
   127		}
   128	
   129		if (!pf->timestamp)
   130			pf->timestamp = iio_get_time_ns(indio_dev);
   131	
   132		mutex_lock(&data->lock);
   133		ret = regmap_read(data->regmap, VCNL4035_ALS_DATA, &als_data);
   134		mutex_unlock(&data->lock);
   135		if (!ret) {
 > 136			als_data = le16_to_cpu(als_data);
   137			iio_push_to_buffers_with_timestamp(indio_dev,
   138							   &als_data,
   139							   pf->timestamp);
   140		} else
   141			dev_err(&data->client->dev,
   142				"Trigger consumer can't read from sensor.\n");
   143		pf->timestamp = 0;
   144	
   145		iio_trigger_notify_done(indio_dev->trig);
   146	
   147		return IRQ_HANDLED;
   148	}
   149	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

  parent reply	other threads:[~2018-06-28 15:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28 12:30 Parthiban Nallathambi
2018-06-28 12:30 ` [PATCH 2/2] iio: light: Add device tree binding " Parthiban Nallathambi
2018-06-28 15:35 ` kbuild test robot [this message]
2018-06-29 15:38 ` [PATCH v2 1/2] iio: light: Add support " Parthiban Nallathambi
2018-06-29 15:38   ` [PATCH v2 2/2] iio: light: Add device tree binding " Parthiban Nallathambi
2018-07-06 20:34     ` Rob Herring
2018-07-07 17:06       ` Parthiban Nallathambi
2018-06-29 23:46   ` [PATCH v2 1/2] iio: light: Add support " kbuild test robot
2018-06-30  9:51   ` Peter Meerwald-Stadler
2018-07-03 12:58     ` Parthiban Nallathambi
2018-08-02  9:52   ` [PATCH v3 " Parthiban Nallathambi
2018-08-02  9:52     ` [PATCH v3 2/2] iio: light: Add device tree binding " Parthiban Nallathambi
2018-08-02 12:51       ` Jonathan Cameron
2018-08-02 12:49     ` [PATCH v3 1/2] iio: light: Add support " Jonathan Cameron
2018-08-02 14:01       ` Parthiban Nallathambi
2018-08-03 22:16         ` Jonathan Cameron
2018-06-29 17:59 ` [PATCH " Jonathan Cameron
2018-07-03 13:35   ` Parthiban Nallathambi
2018-07-07 16:23     ` 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=201806282346.z3EjCFvh%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hs@denx.de \
    --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=mark.rutland@arm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=pmeerw@pmeerw.net \
    --cc=pn@denx.de \
    --cc=robh+dt@kernel.org \
    --cc=sbabic@denx.de \
    --cc=wd@denx.de \
    /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®