From: kernel test robot <lkp@intel.com>
To: Cristian Pop <cristian.pop@analog.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, jic23@kernel.org,
Cristian Pop <cristian.pop@analog.com>
Subject: Re: [PATCH v5] iio: adc: ad7768-1: Add channel label example
Date: Fri, 18 Sep 2020 20:55:10 +0800 [thread overview]
Message-ID: <202009182056.LiUdHLln%lkp@intel.com> (raw)
In-Reply-To: <20200918093356.93670-1-cristian.pop@analog.com>
[-- Attachment #1: Type: text/plain, Size: 2378 bytes --]
Hi Cristian,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on iio/togreg]
[also build test ERROR on linux/master linus/master v5.9-rc5 next-20200918]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Cristian-Pop/iio-adc-ad7768-1-Add-channel-label-example/20200918-190340
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/iio/adc/ad7768-1.c:432:3: error: 'const struct iio_info' has no member named 'read_label'; did you mean 'read_raw'?
432 | .read_label = ad7768_read_label,
| ^~~~~~~~~~
| read_raw
>> drivers/iio/adc/ad7768-1.c:432:16: error: initialization of 'int (*)(struct iio_dev *, const struct iio_chan_spec *, long int)' from incompatible pointer type 'int (*)(struct iio_dev *, const struct iio_chan_spec *, char *)' [-Werror=incompatible-pointer-types]
432 | .read_label = ad7768_read_label,
| ^~~~~~~~~~~~~~~~~
drivers/iio/adc/ad7768-1.c:432:16: note: (near initialization for 'ad7768_info.write_raw_get_fmt')
cc1: some warnings being treated as errors
# https://github.com/0day-ci/linux/commit/6144f5a8d7fa8961b6d39e36092c14301ad823c1
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Cristian-Pop/iio-adc-ad7768-1-Add-channel-label-example/20200918-190340
git checkout 6144f5a8d7fa8961b6d39e36092c14301ad823c1
vim +432 drivers/iio/adc/ad7768-1.c
427
428 static const struct iio_info ad7768_info = {
429 .attrs = &ad7768_group,
430 .read_raw = &ad7768_read_raw,
431 .write_raw = &ad7768_write_raw,
> 432 .read_label = ad7768_read_label,
433 .debugfs_reg_access = &ad7768_reg_access,
434 };
435
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 75935 bytes --]
next prev parent reply other threads:[~2020-09-18 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 9:33 [PATCH v5] iio: adc: ad7768-1: Add channel label example Cristian Pop
2020-09-18 12:55 ` kernel test robot [this message]
2020-09-19 12:17 ` Jonathan Cameron
2020-09-19 15:14 ` Jonathan Cameron
2020-09-19 15:16 ` 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=202009182056.LiUdHLln%lkp@intel.com \
--to=lkp@intel.com \
--cc=cristian.pop@analog.com \
--cc=jic23@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-iio@vger.kernel.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