Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: "Leonard Göhrs" <l.goehrs@pengutronix.de>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	kernel@pengutronix.de, oe-kbuild-all@lists.linux.dev,
	linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH v2 2/2] iio: adc: add ADC driver for the TI LMP92064 controller
Date: Sun, 6 Nov 2022 14:56:35 +0000	[thread overview]
Message-ID: <20221106145635.29716833@jic23-huawei> (raw)
In-Reply-To: <202211011818.QyWLsBVu-lkp@intel.com>

On Tue, 1 Nov 2022 18:36:14 +0800
kernel test robot <lkp@intel.com> wrote:

> Hi Leonard,
> 
> I love your patch! Perhaps something to improve:
> 
> [auto build test WARNING on jic23-iio/togreg]
> [also build test WARNING on linus/master v6.1-rc3 next-20221101]
> [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#_base_tree_information]
> 
> url:    https://github.com/intel-lab-lkp/linux/commits/Leonard-G-hrs/dt-bindings-iio-adc-add-TI-LMP92064-controller/20221101-145036
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
> patch link:    https://lore.kernel.org/r/20221101064804.720050-2-l.goehrs%40pengutronix.de
> patch subject: [PATCH v2 2/2] iio: adc: add ADC driver for the TI LMP92064 controller
> config: x86_64-allyesconfig
> compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
> reproduce (this is a W=1 build):
>         # https://github.com/intel-lab-lkp/linux/commit/4b264b5bc9425f051a3ce5c5a9a30a66d3a0a477
>         git remote add linux-review https://github.com/intel-lab-lkp/linux
>         git fetch --no-tags linux-review Leonard-G-hrs/dt-bindings-iio-adc-add-TI-LMP92064-controller/20221101-145036
>         git checkout 4b264b5bc9425f051a3ce5c5a9a30a66d3a0a477
>         # save the config file
>         mkdir build_dir && cp config build_dir/.config
>         make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/iio/adc/
> 
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
> 
> All warnings (new ones prefixed by >>):
> 
>    drivers/iio/adc/ti-lmp92064.c: In function 'lmp92064_adc_probe':
>    drivers/iio/adc/ti-lmp92064.c:267:15: error: implicit declaration of function 'devm_regulator_get_enable'; did you mean 'devm_regulator_get_optional'? [-Werror=implicit-function-declaration]
>      267 |         ret = devm_regulator_get_enable(dev, "vdd");
>          |               ^~~~~~~~~~~~~~~~~~~~~~~~~
>          |               devm_regulator_get_optional

That's odd. it's definitely in the trees referenced above and there are stubs
for when regulator support isn't built.  No idea... 


>    At top level:
> >> drivers/iio/adc/ti-lmp92064.c:293:35: warning: 'lmp92064_id_table' defined but not used [-Wunused-const-variable=]  
>      293 | static const struct spi_device_id lmp92064_id_table[] = {
>          |                                   ^~~~~~~~~~~~~~~~~
>    cc1: some warnings being treated as errors

This one is obvious though as the relevant entry in the struct spi_driver
is not set.
 
> 
> 
> vim +/lmp92064_id_table +293 drivers/iio/adc/ti-lmp92064.c
> 
>    292	
>  > 293	static const struct spi_device_id lmp92064_id_table[] = {  
>    294		{ "lmp92064", 0 },
>    295		{}
>    296	};
>    297	MODULE_DEVICE_TABLE(spi, lmp92064_id_table);
>    298	
> 


  parent reply	other threads:[~2022-11-06 14:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01  6:48 [PATCH v2 1/2] dt-bindings: iio: adc: add TI LMP92064 controller Leonard Göhrs
2022-11-01  6:48 ` [PATCH v2 2/2] iio: adc: add ADC driver for the " Leonard Göhrs
     [not found]   ` <202211011818.QyWLsBVu-lkp@intel.com>
2022-11-06 14:56     ` Jonathan Cameron [this message]
2022-11-06 15:15   ` Jonathan Cameron
2022-11-01 11:55 ` [PATCH v2 1/2] dt-bindings: iio: adc: add " Rob Herring
2022-11-01 12:28 ` Rob Herring
2022-11-06 14:52   ` 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=20221106145635.29716833@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=l.goehrs@pengutronix.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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