All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v6 3/3] hwmon: (nct6775) Support access via Asus WMI.
Date: Thu, 16 Sep 2021 21:26:15 +0800	[thread overview]
Message-ID: <202109162152.T67ZafGU-lkp@intel.com> (raw)
In-Reply-To: <20210915204251.26081-4-pauk.denis@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2173 bytes --]

Hi Denis,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on groeck-staging/hwmon-next]
[also build test WARNING on v5.15-rc1 next-20210916]
[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/Denis-Pauk/hwmon-Support-access-to-the-NCT677x-via-Asus-WMI/20210916-044449
base:   https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next
config: openrisc-randconfig-r034-20210916 (attached as .config)
compiler: or1k-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/1385f6f898c84efc2f4a9c44107f5a544a771256
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Denis-Pauk/hwmon-Support-access-to-the-NCT677x-via-Asus-WMI/20210916-044449
        git checkout 1385f6f898c84efc2f4a9c44107f5a544a771256
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=openrisc 

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/nct6775.c: In function 'nct6775_wmi_read_value':
>> drivers/hwmon/nct6775.c:200:13: warning: 'tmp' is used uninitialized [-Wuninitialized]
     200 |         u32 tmp;
         |             ^~~


vim +/tmp +200 drivers/hwmon/nct6775.c

   197	
   198	static inline int nct6775_asuswmi_read(u8 bank, u8 reg, u8 *val)
   199	{
 > 200		u32 tmp;
   201		int ret = asuswmi_evaluate_method(ASUSWMI_METHODID_RHWM, bank,
   202					     reg, 0, &tmp);
   203		*val = tmp;
   204		return ret;
   205	}
   206	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 34357 bytes --]

      parent reply	other threads:[~2021-09-16 13:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15 20:42 [PATCH v6 0/3] hwmon: Support access to the NCT677x via Asus WMI Denis Pauk
2021-09-15 20:42 ` [PATCH v6 1/3] hwmon: (nct6775) Use superio_*() function pointers in sio_data Denis Pauk
2021-09-15 20:42 ` [PATCH v6 2/3] hwmon: (nct6775) Use nct6775_*() function pointers in nct6775_data Denis Pauk
2021-09-15 20:42 ` [PATCH v6 3/3] hwmon: (nct6775) Support access via Asus WMI Denis Pauk
2021-09-16  8:34   ` Andy Shevchenko
2021-09-16 13:21     ` Guenter Roeck
2021-09-16 13:23     ` Guenter Roeck
2021-09-16 12:06   ` kernel test robot
2021-09-16 13:26   ` 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=202109162152.T67ZafGU-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.