From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 1/3] hwmon: (asus-ec-sensors) add driver for ASUS EC
Date: Sat, 18 Dec 2021 05:34:10 +0800 [thread overview]
Message-ID: <202112180502.QgAc0Kak-lkp@intel.com> (raw)
In-Reply-To: <20211217164307.1514192-2-eugene.shalygin@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2571 bytes --]
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-20211217]
[cannot apply to linus/master 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/20211218-014433
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/20211218/202112180502.QgAc0Kak-lkp(a)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/f18e6c103f89584b0027d079425d8e868a535a6d
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/20211218-014433
git checkout f18e6c103f89584b0027d079425d8e868a535a6d
# 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:45: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Arbitrary set max. allowed bank number. Required for sorting banks and
drivers/hwmon/asus-ec-sensors.c:133: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* All the known sensors for ASUS EC controllers
vim +45 drivers/hwmon/asus-ec-sensors.c
43
44 /**
> 45 * Arbitrary set max. allowed bank number. Required for sorting banks and
46 * currently is overkill with just 2 banks used at max, but for the sake
47 * of alignment let's set it to a higher value.
48 */
49 #define ASUS_EC_MAX_BANK 3
50
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next prev parent reply other threads:[~2021-12-17 21:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
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:34 ` kernel test robot [this message]
2021-12-17 21:52 ` Guenter Roeck
2021-12-17 22:33 ` Eugene Shalygin
2021-12-17 23:47 ` Guenter Roeck
2021-12-17 16:43 ` [PATCH 2/3] hwmon: (asus-ec-sensors) update documentation Eugene Shalygin
2021-12-17 16:43 ` [PATCH 3/3] hwmon: (asus_wmi_ec_sensors) remove the driver Eugene Shalygin
-- strict thread matches above, loose matches on Subject: below --
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
2021-12-16 20:53 Eugene Shalygin
2021-12-16 21:27 ` 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
2021-12-17 4:35 ` kernel test robot
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=202112180502.QgAc0Kak-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.