From: kernel test robot <lkp@intel.com>
To: Saravanan Sekar <saravanan@linumiz.com>,
sravanhome@gmail.com, lgirdwood@gmail.com, broonie@kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, linux@roeck-us.net, jdelvare@suse.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-hwmon@vger.kernel.org,
Saravanan Sekar <saravanan@linumiz.com>
Subject: Re: [PATCH 1/3] hwmon: (pmbus/mpq7932) Get page count based on chip info
Date: Mon, 11 Sep 2023 14:40:55 +0800 [thread overview]
Message-ID: <202309111406.BSKHGe9U-lkp@intel.com> (raw)
In-Reply-To: <20230911034150.181880-2-saravanan@linumiz.com>
Hi Saravanan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on groeck-staging/hwmon-next]
[also build test WARNING on broonie-regulator/for-next linus/master v6.6-rc1 next-20230911]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Saravanan-Sekar/hwmon-pmbus-mpq7932-Get-page-count-based-on-chip-info/20230911-114451
base: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next
patch link: https://lore.kernel.org/r/20230911034150.181880-2-saravanan%40linumiz.com
patch subject: [PATCH 1/3] hwmon: (pmbus/mpq7932) Get page count based on chip info
config: x86_64-randconfig-005-20230911 (https://download.01.org/0day-ci/archive/20230911/202309111406.BSKHGe9U-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230911/202309111406.BSKHGe9U-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202309111406.BSKHGe9U-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/hwmon/pmbus/mpq7932.c:108:16: warning: cast to smaller integer type 'int' from 'const void *' [-Wvoid-pointer-to-int-cast]
info->pages = (int)device_get_match_data(&client->dev);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 warning generated.
vim +108 drivers/hwmon/pmbus/mpq7932.c
95
96 static int mpq7932_probe(struct i2c_client *client)
97 {
98 struct mpq7932_data *data;
99 struct pmbus_driver_info *info;
100 struct device *dev = &client->dev;
101 int i;
102
103 data = devm_kzalloc(dev, sizeof(struct mpq7932_data), GFP_KERNEL);
104 if (!data)
105 return -ENOMEM;
106
107 info = &data->info;
> 108 info->pages = (int)device_get_match_data(&client->dev);
109 info->format[PSC_VOLTAGE_OUT] = direct;
110 info->m[PSC_VOLTAGE_OUT] = 160;
111 info->b[PSC_VOLTAGE_OUT] = -33;
112 for (i = 0; i < info->pages; i++) {
113 info->func[i] = PMBUS_HAVE_VOUT | PMBUS_HAVE_STATUS_VOUT
114 | PMBUS_HAVE_STATUS_TEMP;
115 }
116
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-09-11 6:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 3:41 [PATCH 0/3] Add support for mpq2286 PMIC IC Saravanan Sekar
2023-09-11 3:41 ` [PATCH 1/3] hwmon: (pmbus/mpq7932) Get page count based on chip info Saravanan Sekar
2023-09-11 4:24 ` Guenter Roeck
2023-09-11 5:46 ` kernel test robot
2023-09-11 6:40 ` kernel test robot [this message]
2023-09-11 3:41 ` [PATCH 2/3] dt-bindings: regulator: Add mps,mpq2286 power-management IC Saravanan Sekar
2023-09-11 4:10 ` Rob Herring
2023-09-11 4:28 ` Guenter Roeck
2023-09-11 6:26 ` Krzysztof Kozlowski
2023-09-11 7:12 ` Saravanan Sekar
2023-09-11 7:41 ` Krzysztof Kozlowski
2023-09-11 3:41 ` [PATCH 3/3] hwmon: (pmbus/mpq2286) Add a support for mpq2286 Power Management IC Saravanan Sekar
2023-09-11 4:23 ` Guenter Roeck
2023-09-26 15:14 ` Saravanan Sekar
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=202309111406.BSKHGe9U-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh+dt@kernel.org \
--cc=saravanan@linumiz.com \
--cc=sravanhome@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;
as well as URLs for NNTP newsgroup(s).