From: kernel test robot <lkp@intel.com>
To: Eugene Shalygin <eugene.shalygin@gmail.com>
Cc: kbuild-all@lists.01.org, andy.shevchenko@gmail.com,
pauk.denis@gmail.com, Eugene Shalygin <eugene.shalygin@gmail.com>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org
Subject: Re: [PATCH 1/3] hwmon: (asus-ec-sensors) add driver for ASUS EC
Date: Fri, 17 Dec 2021 12:35:03 +0800 [thread overview]
Message-ID: <202112171205.FwhZfLkY-lkp@intel.com> (raw)
In-Reply-To: <20211216205303.768991-1-eugene.shalygin@gmail.com>
Hi Eugene,
I love your patch! Perhaps something to improve:
[auto build test WARNING on groeck-staging/hwmon-next]
[also build test WARNING on next-20211215]
[cannot apply to v5.16-rc5]
[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/Eugene-Shalygin/hwmon-asus-ec-sensors-add-driver-for-ASUS-EC/20211217-045428
base: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next
config: ia64-allyesconfig (https://download.01.org/0day-ci/archive/20211217/202112171205.FwhZfLkY-lkp@intel.com/config)
compiler: ia64-linux-gcc (GCC) 11.2.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/27e7f47121cb02208740ed895a4cf4c7ab5bee63
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Eugene-Shalygin/hwmon-asus-ec-sensors-add-driver-for-ASUS-EC/20211217-045428
git checkout 27e7f47121cb02208740ed895a4cf4c7ab5bee63
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=ia64 SHELL=/bin/bash drivers/hwmon/
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 >>):
drivers/hwmon/asus-ec-sensors.c: In function 'asus_ec_probe':
>> drivers/hwmon/asus-ec-sensors.c:690:26: warning: ordered comparison of pointer with integer zero [-Wextra]
690 | if (state->board < 0) {
| ^
vim +690 drivers/hwmon/asus-ec-sensors.c
685
686 static int asus_ec_probe(struct platform_device *pdev)
687 {
688 struct ec_sensors_data *state = platform_get_drvdata(pdev);
689
> 690 if (state->board < 0) {
691 return -ENODEV;
692 }
693
694 return 0;
695 }
696
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2021-12-17 4:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 20:53 [PATCH 1/3] hwmon: (asus-ec-sensors) add driver for ASUS EC Eugene Shalygin
2021-12-16 20:53 ` [PATCH 2/3] hwmon: update ASUS EC driver documentation Eugene Shalygin
2021-12-16 20:53 ` [PATCH 3/3] hwmon: remove asus_wmi_ec_sensors driver Eugene Shalygin
2021-12-16 21:40 ` Denis Pauk
2021-12-16 21:27 ` [PATCH 1/3] hwmon: (asus-ec-sensors) add driver for ASUS EC Andy Shevchenko
2021-12-16 22:04 ` Denis Pauk
2021-12-16 22:58 ` Eugene Shalygin
2021-12-18 18:48 ` Denis Pauk
2021-12-17 0:07 ` Eugene Shalygin
2021-12-17 4:35 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-17 16:43 PATCH v2 ASUS EC Sensors Eugene Shalygin
2021-12-17 16:43 ` [PATCH 1/3] hwmon: (asus-ec-sensors) add driver for ASUS EC Eugene Shalygin
2021-12-17 21:52 ` Guenter Roeck
2021-12-17 22:33 ` Eugene Shalygin
2021-12-17 23:47 ` Guenter Roeck
2022-01-11 16:08 PATCH v3 ASUS EC Sensors Eugene Shalygin
2022-01-11 16:08 ` [PATCH 1/3] hwmon: (asus-ec-sensors) add driver for ASUS EC Eugene Shalygin
2022-01-11 16:33 ` Guenter Roeck
2022-01-11 17:04 ` Guenter Roeck
2022-01-11 17:22 ` Eugene Shalygin
2022-01-11 18:43 ` Guenter Roeck
2022-01-11 18:52 ` Eugene Shalygin
2022-01-11 19:15 ` Guenter Roeck
2022-01-11 19:18 ` Eugene Shalygin
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=202112171205.FwhZfLkY-lkp@intel.com \
--to=lkp@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=eugene.shalygin@gmail.com \
--cc=jdelvare@suse.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=pauk.denis@gmail.com \
/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