public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: Alexandru Ardelean <aardelean@baylibre.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, oe-kbuild-all@lists.linux.dev,
	krzk+dt@kernel.org, robh@kernel.org, lars@metafoo.de,
	michael.hennerich@analog.com, gstols@baylibre.com,
	dlechner@baylibre.com
Subject: Re: [PATCH v6 8/8] iio: adc: ad7606: add support for AD7606C-{16,18} parts
Date: Sat, 14 Sep 2024 15:41:50 +0100	[thread overview]
Message-ID: <20240914154150.6ce9c1b6@jic23-huawei> (raw)
In-Reply-To: <202409140416.KWHXjFSv-lkp@intel.com>

On Sat, 14 Sep 2024 04:30:42 +0800
kernel test robot <lkp@intel.com> wrote:

> Hi Alexandru,
> 
> kernel test robot noticed the following build warnings:
> 
> [auto build test WARNING on jic23-iio/togreg]
> [also build test WARNING on next-20240913]
> [cannot apply to linus/master v6.11-rc7]
> [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/Alexandru-Ardelean/iio-adc-ad7606-add-bits-parameter-to-channels-macros/20240913-220501
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
> patch link:    https://lore.kernel.org/r/20240913135744.152669-9-aardelean%40baylibre.com
> patch subject: [PATCH v6 8/8] iio: adc: ad7606: add support for AD7606C-{16,18} parts
> config: arm-randconfig-001-20240914 (https://download.01.org/0day-ci/archive/20240914/202409140416.KWHXjFSv-lkp@intel.com/config)
> compiler: arm-linux-gnueabi-gcc (GCC) 14.1.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240914/202409140416.KWHXjFSv-lkp@intel.com/reproduce)
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202409140416.KWHXjFSv-lkp@intel.com/
> 
> All warnings (new ones prefixed by >>):
> 
> >> drivers/iio/adc/ad7606.c:39:27: warning: 'ad7606_18bit_hw_scale_avail' defined but not used [-Wunused-const-variable=]  
>       39 | static const unsigned int ad7606_18bit_hw_scale_avail[2] = {
>          |                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> 
> vim +/ad7606_18bit_hw_scale_avail +39 drivers/iio/adc/ad7606.c
> 
>     38	
>   > 39	static const unsigned int ad7606_18bit_hw_scale_avail[2] = {  
>     40		38147, 76294
>     41	};
>     42	
Hmm. Seems like there is no code that would use this, so what is it
and where did the numbers come from?

Jonathan

> 


  reply	other threads:[~2024-09-14 14:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13 13:57 [PATCH v6 0/8] iio: adc: ad7606: add support for AD7606C-{16,18} parts Alexandru Ardelean
2024-09-13 13:57 ` [PATCH v6 1/8] iio: adc: ad7606: add 'bits' parameter to channels macros Alexandru Ardelean
2024-09-13 13:57 ` [PATCH v6 2/8] iio: adc: ad7606: move 'val' pointer to ad7606_scan_direct() Alexandru Ardelean
2024-09-13 13:57 ` [PATCH v6 3/8] iio: adc: ad7606: move scale_setup as function pointer on chip-info Alexandru Ardelean
2024-09-13 13:57 ` [PATCH v6 4/8] iio: adc: ad7606: wrap channel ranges & scales into struct Alexandru Ardelean
2024-09-13 13:57 ` [PATCH v6 5/8] iio: adc: ad7606: rework available attributes for SW channels Alexandru Ardelean
2024-09-13 13:57 ` [PATCH v6 6/8] dt-bindings: iio: adc: document diff-channels corner case for some ADCs Alexandru Ardelean
2024-09-13 13:57 ` [PATCH v6 7/8] dt-bindings: iio: adc: add docs for AD7606C-{16,18} parts Alexandru Ardelean
2024-09-13 13:57 ` [PATCH v6 8/8] iio: adc: ad7606: add support " Alexandru Ardelean
2024-09-13 20:30   ` kernel test robot
2024-09-14 14:41     ` Jonathan Cameron [this message]
2024-09-16  6:38       ` Alexandru Ardelean
2024-09-13 21:22   ` kernel test robot
2024-09-14 14:45 ` [PATCH v6 0/8] " 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=20240914154150.6ce9c1b6@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=aardelean@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=gstols@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=michael.hennerich@analog.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=robh@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