From: kernel test robot <lkp@intel.com>
To: Michael Walle <michael@walle.cc>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: kbuild-all@lists.01.org, linux-hwmon@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Walle <michael@walle.cc>
Subject: Re: [PATCH v1 4/4] hwmon: add driver for the Microchip LAN966x SoC
Date: Sun, 27 Mar 2022 11:13:41 +0800 [thread overview]
Message-ID: <202203271141.S44Wx3yF-lkp@intel.com> (raw)
In-Reply-To: <20220326192347.2940747-5-michael@walle.cc>
Hi Michael,
I love your patch! Perhaps something to improve:
[auto build test WARNING on groeck-staging/hwmon-next]
[also build test WARNING on robh/for-next linus/master v5.17 next-20220325]
[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/intel-lab-lkp/linux/commits/Michael-Walle/hwmon-add-lan9668-driver/20220327-032606
base: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next
config: sparc64-randconfig-s031-20220327 (https://download.01.org/0day-ci/archive/20220327/202203271141.S44Wx3yF-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 11.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://github.com/intel-lab-lkp/linux/commit/cfef456b1f1b1ab545a03f098e209aff8ae507b7
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Michael-Walle/hwmon-add-lan9668-driver/20220327-032606
git checkout cfef456b1f1b1ab545a03f098e209aff8ae507b7
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=sparc64 SHELL=/bin/bash drivers/hwmon/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/hwmon/lan966x-hwmon.c:302:24: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected struct regmap * @@ got void [noderef] __iomem *[assigned] base @@
drivers/hwmon/lan966x-hwmon.c:302:24: sparse: expected struct regmap *
drivers/hwmon/lan966x-hwmon.c:302:24: sparse: got void [noderef] __iomem *[assigned] base
vim +302 drivers/hwmon/lan966x-hwmon.c
289
290 static struct regmap *lan966x_init_regmap(struct platform_device *pdev,
291 const char *name)
292 {
293 struct regmap_config regmap_config = {
294 .reg_bits = 32,
295 .reg_stride = 4,
296 .val_bits = 32,
297 };
298 void __iomem *base;
299
300 base = devm_platform_ioremap_resource_byname(pdev, name);
301 if (IS_ERR(base))
> 302 return base;
303
304 regmap_config.name = name;
305
306 return devm_regmap_init_mmio(&pdev->dev, base, ®map_config);
307 }
308
--
0-DAY CI Kernel Test Service
https://01.org/lkp
prev parent reply other threads:[~2022-03-27 3:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 19:23 [PATCH v1 0/4] hwmon: add lan9668 driver Michael Walle
2022-03-26 19:23 ` [PATCH v1 1/4] lib: add generic polynomial calculation Michael Walle
2022-03-27 1:21 ` Guenter Roeck
2022-03-26 19:23 ` [PATCH v1 2/4] hwmon: (bt1-pvt) use generic polynomial functions Michael Walle
2022-03-27 0:49 ` kernel test robot
2022-03-27 1:10 ` kernel test robot
2022-03-27 1:22 ` Guenter Roeck
2022-03-26 19:23 ` [PATCH v1 3/4] dt-bindings: hwmon: add Microchip LAN966x bindings Michael Walle
2022-03-27 11:17 ` Krzysztof Kozlowski
2022-03-26 19:23 ` [PATCH v1 4/4] hwmon: add driver for the Microchip LAN966x SoC Michael Walle
2022-03-27 1:34 ` Guenter Roeck
2022-03-27 14:18 ` Michael Walle
2022-03-27 18:22 ` Guenter Roeck
2022-03-28 11:28 ` Michael Walle
2022-03-28 16:37 ` Guenter Roeck
2022-03-27 3:13 ` kernel test robot [this message]
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=202203271141.S44Wx3yF-lkp@intel.com \
--to=lkp@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=kbuild-all@lists.01.org \
--cc=krzk@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=michael@walle.cc \
--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).