devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Gene Chen <gene.chen.richtek@gmail.com>,
	jic23@kernel.org, robh+dt@kernel.org, matthias.bgg@gmail.com
Cc: kbuild-all@lists.01.org, knaack.h@gmx.de, lars@metafoo.de,
	pmeerw@pmeerw.net, devicetree@vger.kernel.org,
	linux-iio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v6 3/3] iio: adc: mt6360: Add ADC driver for MT6360
Date: Wed, 30 Sep 2020 19:12:13 +0800	[thread overview]
Message-ID: <202009301905.ns1B9LpF-lkp@intel.com> (raw)
In-Reply-To: <1601542448-7433-4-git-send-email-gene.chen.richtek@gmail.com>

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

Hi Gene,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on iio/togreg]
[also build test ERROR on robh/for-next soc/for-next v5.9-rc7 next-20200929]
[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/Gene-Chen/iio-adc-mt6360-Add-ADC-driver-for-MT6360/20200930-165619
base:   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
config: sh-allmodconfig (attached as .config)
compiler: sh4-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/0day-ci/linux/commit/c5eda86258a6e9fc21bae8a1e0cb3bc9f54ca87e
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Gene-Chen/iio-adc-mt6360-Add-ADC-driver-for-MT6360/20200930-165619
        git checkout c5eda86258a6e9fc21bae8a1e0cb3bc9f54ca87e
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=sh 

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/mt6360-adc.c:212:3: error: 'const struct iio_info' has no member named 'read_label'; did you mean 'read_raw'?
     212 |  .read_label = mt6360_adc_read_label,
         |   ^~~~~~~~~~
         |   read_raw
>> drivers/iio/adc/mt6360-adc.c:212:16: error: initialization of 'int (*)(struct iio_dev *, const struct iio_chan_spec *, int,  int *, int *, long int)' from incompatible pointer type 'int (*)(struct iio_dev *, const struct iio_chan_spec *, char *)' [-Werror=incompatible-pointer-types]
     212 |  .read_label = mt6360_adc_read_label,
         |                ^~~~~~~~~~~~~~~~~~~~~
   drivers/iio/adc/mt6360-adc.c:212:16: note: (near initialization for 'mt6360_adc_iio_info.read_raw_multi')
   cc1: some warnings being treated as errors

vim +212 drivers/iio/adc/mt6360-adc.c

   209	
   210	static const struct iio_info mt6360_adc_iio_info = {
   211		.read_raw = mt6360_adc_read_raw,
 > 212		.read_label = mt6360_adc_read_label,
   213	};
   214	

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

  reply	other threads:[~2020-09-30 11:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01  8:54 [PATCH v6 0/3] iio: adc: mt6360: Add ADC driver for MT6360 Gene Chen
2020-10-01  8:54 ` [PATCH v6 1/3] dt-bindings: iio: adc: add bindings doc for MT6360 ADC Gene Chen
2020-10-05 14:38   ` Rob Herring
2020-10-01  8:54 ` [PATCH v6 2/3] Documentation: ABI: testing: mt6360: Add ADC sysfs guideline Gene Chen
2020-10-01  8:54 ` [PATCH v6 3/3] iio: adc: mt6360: Add ADC driver for MT6360 Gene Chen
2020-09-30 11:12   ` kernel test robot [this message]
2020-10-16 15:28   ` Andy Shevchenko
2020-10-10 16:57 ` [PATCH v6 0/3] " 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=202009301905.ns1B9LpF-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gene.chen.richtek@gmail.com \
    --cc=jic23@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).