From: kbuild test robot <lkp@intel.com>
To: Crestez Dan Leonard <leonard.crestez@intel.com>
Cc: kbuild-all@01.org, Jonathan Cameron <jic23@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Daniel Baluta <daniel.baluta@intel.com>,
Crestez Dan Leonard <leonard.crestez@intel.com>
Subject: Re: [PATCH v2 2/2] ti-adc081c: Initial triggered buffer support
Date: Tue, 5 Apr 2016 02:39:33 +0800 [thread overview]
Message-ID: <201604050256.6q5PQlT3%fengguang.wu@intel.com> (raw)
In-Reply-To: <d2d8157e906c428111752c36d13e35815f6dc194.1459793615.git.leonard.crestez@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2026 bytes --]
Hi Crestez,
[auto build test WARNING on iio/togreg]
[also build test WARNING on v4.6-rc2 next-20160404]
[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/Add-support-for-adc101c-and-adc121c/20160405-022459
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
config: s390-allmodconfig (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/adc/ti-adc081c.c: In function 'adc081c_trigger_handler':
>> drivers/iio/adc/ti-adc081c.c:130:1: warning: 'adc081c_trigger_handler' uses dynamic stack allocation
}
^
vim +/adc081c_trigger_handler +130 drivers/iio/adc/ti-adc081c.c
114 static irqreturn_t adc081c_trigger_handler(int irq, void *p)
115 {
116 struct iio_poll_func *pf = p;
117 struct iio_dev *indio_dev = pf->indio_dev;
118 struct adc081c *data = iio_priv(indio_dev);
119 u16 buf[indio_dev->scan_bytes / 2];
120 int ret;
121
122 ret = i2c_smbus_read_word_swapped(data->i2c, REG_CONV_RES);
123 if (ret < 0)
124 goto out;
125 buf[0] = ret;
126 iio_push_to_buffers_with_timestamp(indio_dev, buf, iio_get_time_ns());
127 out:
128 iio_trigger_notify_done(indio_dev->trig);
129 return IRQ_HANDLED;
> 130 }
131
132 static int adc081c_probe(struct i2c_client *client,
133 const struct i2c_device_id *id)
134 {
135 struct iio_dev *iio;
136 struct adc081c *adc;
137 struct adcxx1c_model *model = (struct adcxx1c_model*)id->driver_data;
138 int err;
---
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: 40033 bytes --]
next prev parent reply other threads:[~2016-04-04 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 18:21 [PATCH v2 0/2] Add support for adc101c* and adc121c* Crestez Dan Leonard
2016-04-04 18:21 ` [PATCH v2 1/2] ti-adc081c: " Crestez Dan Leonard
2016-04-10 14:25 ` Jonathan Cameron
2016-04-04 18:21 ` [PATCH v2 2/2] ti-adc081c: Initial triggered buffer support Crestez Dan Leonard
2016-04-04 18:39 ` kbuild test robot [this message]
2016-04-10 14:29 ` 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=201604050256.6q5PQlT3%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=daniel.baluta@intel.com \
--cc=jic23@kernel.org \
--cc=kbuild-all@01.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=leonard.crestez@intel.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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®