From: kernel test robot <lkp@intel.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Jonathan Cameron <jic23@kernel.org>
Cc: kbuild-all@lists.01.org, Oleksij Rempel <o.rempel@pengutronix.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Pengutronix Kernel Team <kernel@pengutronix.de>,
David Jander <david@protonic.nl>,
Robin van der Gracht <robin@protonic.nl>,
linux-iio@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v2 3/3] iio: adc: add ADC driver for the TI TSC2046 controller
Date: Sat, 13 Mar 2021 01:49:40 +0800 [thread overview]
Message-ID: <202103130147.yfJqKGPe-lkp@intel.com> (raw)
In-Reply-To: <20210312105515.32055-4-o.rempel@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 4383 bytes --]
Hi Oleksij,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linux/master]
[also build test WARNING on linus/master v5.12-rc2]
[cannot apply to iio/togreg]
[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/Oleksij-Rempel/mainline-ti-tsc2046-adc-driver/20210312-185657
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git a74e6a014c9d4d4161061f770c9b4f98372ac778
config: riscv-allyesconfig (attached as .config)
compiler: riscv64-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/7c34f2cd7f0176071b53152c6065f6d5a078463b
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Oleksij-Rempel/mainline-ti-tsc2046-adc-driver/20210312-185657
git checkout 7c34f2cd7f0176071b53152c6065f6d5a078463b
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from include/linux/device.h:15,
from include/linux/node.h:18,
from include/linux/cpu.h:17,
from include/linux/cacheinfo.h:6,
from arch/riscv/include/asm/cacheinfo.h:9,
from arch/riscv/include/asm/elf.h:14,
from include/linux/elf.h:6,
from include/linux/module.h:18,
from drivers/iio/adc/ti-tsc2046.c:10:
drivers/iio/adc/ti-tsc2046.c: In function 'tsc2046_adc_parse_fwnode':
>> drivers/iio/adc/ti-tsc2046.c:579:17: warning: format '%i' expects argument of type 'int', but argument 5 has type 'long unsigned int' [-Wformat=]
579 | dev_err(dev, "%pfw: Unsupported reg value: %i, max supported is: %i.\n",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/dev_printk.h:19:22: note: in definition of macro 'dev_fmt'
19 | #define dev_fmt(fmt) fmt
| ^~~
drivers/iio/adc/ti-tsc2046.c:579:4: note: in expansion of macro 'dev_err'
579 | dev_err(dev, "%pfw: Unsupported reg value: %i, max supported is: %i.\n",
| ^~~~~~~
drivers/iio/adc/ti-tsc2046.c:579:70: note: format string is defined here
579 | dev_err(dev, "%pfw: Unsupported reg value: %i, max supported is: %i.\n",
| ~^
| |
| int
| %li
vim +579 drivers/iio/adc/ti-tsc2046.c
561
562 static void tsc2046_adc_parse_fwnode(struct tsc2046_adc_priv *priv)
563 {
564 struct fwnode_handle *child;
565 struct device *dev = &priv->spi->dev;
566
567 device_for_each_child_node(dev, child) {
568 u32 stl, aver, reg;
569 int ret;
570
571 ret = fwnode_property_read_u32(child, "reg", ®);
572 if (ret) {
573 dev_err(dev, "invalid reg on %pfw, err: %pe\n", child,
574 ERR_PTR(ret));
575 continue;
576 }
577
578 if (reg >= ARRAY_SIZE(priv->ch_cfg)) {
> 579 dev_err(dev, "%pfw: Unsupported reg value: %i, max supported is: %i.\n",
580 child, reg, ARRAY_SIZE(priv->ch_cfg));
581 continue;
582 }
583
584 ret = fwnode_property_read_u32(child, "settling-time-us", &stl);
585 if (!ret)
586 priv->ch_cfg[reg].settling_time_us = stl;
587
588 ret = fwnode_property_read_u32(child, "average-samples", &aver);
589 if (!ret)
590 priv->ch_cfg[reg].average_samples = aver;
591 }
592 }
593
---
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: 68974 bytes --]
next prev parent reply other threads:[~2021-03-12 17:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 10:55 [PATCH v2 0/3] mainline ti tsc2046 adc driver Oleksij Rempel
2021-03-12 10:55 ` [PATCH v2 1/3] dt-bindings:iio:adc: add generic settling-time-us and average-samples channel properties Oleksij Rempel
2021-03-13 15:15 ` Jonathan Cameron
2021-03-12 10:55 ` [PATCH v2 2/3] dt-bindings:iio:adc: add documentation for TI TSC2046 controller Oleksij Rempel
2021-03-15 16:20 ` Rob Herring
2021-03-12 10:55 ` [PATCH v2 3/3] iio: adc: add ADC driver for the " Oleksij Rempel
2021-03-12 15:32 ` Andy Shevchenko
2021-03-12 17:49 ` kernel test robot [this message]
2021-03-13 16:11 ` Jonathan Cameron
2021-03-16 5:57 ` Oleksij Rempel
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=202103130147.yfJqKGPe-lkp@intel.com \
--to=lkp@intel.com \
--cc=david@protonic.nl \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=kernel@pengutronix.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=robin@protonic.nl \
/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).