From: kernel test robot <lkp@intel.com>
To: Naresh Solanki <naresh.solanki@9elements.com>,
Guenter Roeck <linux@roeck-us.net>,
linux-hwmon@vger.kernel.org, Jean Delvare <jdelvare@suse.com>
Cc: oe-kbuild-all@lists.linux.dev,
Patrick Rudolph <patrick.rudolph@9elements.com>,
Naresh Solanki <Naresh.Solanki@9elements.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] hwmon: (pmbus/core): Add regulator event support
Date: Tue, 28 Mar 2023 21:59:12 +0800 [thread overview]
Message-ID: <202303282129.T1h4aFZp-lkp@intel.com> (raw)
In-Reply-To: <20230328121712.4057359-2-Naresh.Solanki@9elements.com>
Hi Naresh,
I love your patch! Yet something to improve:
[auto build test ERROR on 8a863eb1b1162653d133856702e13560f3596b85]
url: https://github.com/intel-lab-lkp/linux/commits/Naresh-Solanki/hwmon-pmbus-core-Add-regulator-event-support/20230328-201831
base: 8a863eb1b1162653d133856702e13560f3596b85
patch link: https://lore.kernel.org/r/20230328121712.4057359-2-Naresh.Solanki%409elements.com
patch subject: [PATCH 2/3] hwmon: (pmbus/core): Add regulator event support
config: riscv-allmodconfig (https://download.01.org/0day-ci/archive/20230328/202303282129.T1h4aFZp-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 12.1.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/intel-lab-lkp/linux/commit/bc5ab0ded8947e49f5292c04bf381274a0272f3f
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Naresh-Solanki/hwmon-pmbus-core-Add-regulator-event-support/20230328-201831
git checkout bc5ab0ded8947e49f5292c04bf381274a0272f3f
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=riscv olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash drivers/hwmon/pmbus/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202303282129.T1h4aFZp-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
drivers/hwmon/pmbus/pmbus_core.c: In function 'pmbus_regulator_get_error_flags':
>> drivers/hwmon/pmbus/pmbus_core.c:2938:9: warning: the address of 'event' will always evaluate as 'true' [-Waddress]
2938 | return pmbus_get_flags(data, rdev_get_id(rdev), flags, &event, false);
| ^~~~~~
>> drivers/hwmon/pmbus/pmbus_core.c:2938:16: error: too many arguments to function 'pmbus_get_flags'
2938 | return pmbus_get_flags(data, rdev_get_id(rdev), flags, &event, false);
| ^~~~~~~~~~~~~~~
drivers/hwmon/pmbus/pmbus_core.c:2886:27: note: declared here
2886 | static int __maybe_unused pmbus_get_flags(struct pmbus_data *data, u8 page, unsigned int *flags,
| ^~~~~~~~~~~~~~~
vim +/pmbus_get_flags +2938 drivers/hwmon/pmbus/pmbus_core.c
2930
2931 static int pmbus_regulator_get_error_flags(struct regulator_dev *rdev, unsigned int *flags)
2932 {
2933 struct device *dev = rdev_get_dev(rdev);
2934 struct i2c_client *client = to_i2c_client(dev->parent);
2935 struct pmbus_data *data = i2c_get_clientdata(client);
2936 int event;
2937
> 2938 return pmbus_get_flags(data, rdev_get_id(rdev), flags, &event, false);
2939 }
2940
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-03-28 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 12:17 [PATCH 1/3] hwmon: (pmbus/core): Add rdev in pmbus_data struct Naresh Solanki
2023-03-28 12:17 ` [PATCH 2/3] hwmon: (pmbus/core): Add regulator event support Naresh Solanki
2023-03-28 13:59 ` kernel test robot [this message]
2023-03-28 12:17 ` [PATCH 3/3] hwmon: (pmbus/core): Notify regulator events Naresh Solanki
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=202303282129.T1h4aFZp-lkp@intel.com \
--to=lkp@intel.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=naresh.solanki@9elements.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=patrick.rudolph@9elements.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
all inboxes | Powered by JetHome®