Re: [PATCH 5/5] max44000: Initial triggered buffer support

From: kbuild test robot
Date: Thu Apr 07 2016 - 17:57:33 EST


Hi Crestez,

[auto build test WARNING on iio/togreg]
[also build test WARNING on v4.6-rc2 next-20160407]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]

url: https://github.com/0day-ci/linux/commits/Crestez-Dan-Leonard/Support-for-max44000-Ambient-and-Infrared-Proximity-Sensor/20160408-003121
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
config: s390-allyesconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=s390

All warnings (new ones prefixed by >>):

drivers/iio/light/max44000.c: In function 'max44000_trigger_handler':
>> drivers/iio/light/max44000.c:513:1: warning: 'max44000_trigger_handler' uses dynamic stack allocation
}
^

vim +/max44000_trigger_handler +513 drivers/iio/light/max44000.c

497 if (*indio_dev->active_scan_mask & (1 << MAX44000_SCAN_INDEX_PRX)) {
498 ret = regmap_read(data->regmap, MAX44000_REG_PRX_DATA, &regval);
499 if (ret < 0)
500 goto out_unlock;
501 *pos = regval;
502 }
503 mutex_unlock(&data->lock);
504
505 iio_push_to_buffers_with_timestamp(indio_dev, buf, iio_get_time_ns());
506 iio_trigger_notify_done(indio_dev->trig);
507 return IRQ_HANDLED;
508
509 out_unlock:
510 mutex_unlock(&data->lock);
511 iio_trigger_notify_done(indio_dev->trig);
512 return IRQ_HANDLED;
> 513 }
514
515 static int max44000_probe(struct i2c_client *client,
516 const struct i2c_device_id *id)
517 {
518 struct max44000_data *data;
519 struct iio_dev *indio_dev;
520 int ret, reg;
521

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

Attachment: .config.gz
Description: Binary data