From: kernel test robot <lkp@intel.com>
To: Dzmitry Sankouski <dsankouski@gmail.com>,
Sebastian Reichel <sre@kernel.org>,
Chanwoo Choi <cw00.choi@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>, Lee Jones <lee@kernel.org>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Pavel Machek <pavel@ucw.cz>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-input@vger.kernel.org,
linux-leds@vger.kernel.org,
Dzmitry Sankouski <dsankouski@gmail.com>
Subject: Re: [PATCH v6 6/7] power: supply: max77705: Add fuel gauge driver for Maxim 77705
Date: Fri, 11 Oct 2024 04:45:59 +0800 [thread overview]
Message-ID: <202410110404.etzjIhE5-lkp@intel.com> (raw)
In-Reply-To: <20241007-starqltechn_integration_upstream-v6-6-0d38b5090c57@gmail.com>
Hi Dzmitry,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 58ca61c1a866bfdaa5e19fb19a2416764f847d75]
url: https://github.com/intel-lab-lkp/linux/commits/Dzmitry-Sankouski/power-supply-add-undervoltage-health-status-property/20241008-000014
base: 58ca61c1a866bfdaa5e19fb19a2416764f847d75
patch link: https://lore.kernel.org/r/20241007-starqltechn_integration_upstream-v6-6-0d38b5090c57%40gmail.com
patch subject: [PATCH v6 6/7] power: supply: max77705: Add fuel gauge driver for Maxim 77705
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20241011/202410110404.etzjIhE5-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241011/202410110404.etzjIhE5-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/202410110404.etzjIhE5-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/power/supply/max77705_fuel_gauge.c:220:7: warning: variable 'ret' is used uninitialized whenever switch case is taken [-Wsometimes-uninitialized]
220 | case POWER_SUPPLY_PROP_MANUFACTURER:
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/power/supply/max77705_fuel_gauge.c:227:6: note: uninitialized use occurs here
227 | if (ret)
| ^~~
drivers/power/supply/max77705_fuel_gauge.c:217:7: warning: variable 'ret' is used uninitialized whenever switch case is taken [-Wsometimes-uninitialized]
217 | case POWER_SUPPLY_PROP_MODEL_NAME:
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/power/supply/max77705_fuel_gauge.c:227:6: note: uninitialized use occurs here
227 | if (ret)
| ^~~
drivers/power/supply/max77705_fuel_gauge.c:169:9: note: initialize the variable 'ret' to silence this warning
169 | int ret;
| ^
| = 0
2 warnings generated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for MODVERSIONS
Depends on [n]: MODULES [=y] && !COMPILE_TEST [=y]
Selected by [y]:
- RANDSTRUCT_FULL [=y] && (CC_HAS_RANDSTRUCT [=y] || GCC_PLUGINS [=n]) && MODULES [=y]
vim +/ret +220 drivers/power/supply/max77705_fuel_gauge.c
162
163 static int max77705_fg_get_property(struct power_supply *psy,
164 enum power_supply_property psp,
165 union power_supply_propval *val)
166 {
167 struct max77705_fuelgauge_data *fuelgauge =
168 power_supply_get_drvdata(psy);
169 int ret;
170
171 switch (psp) {
172 case POWER_SUPPLY_PROP_STATUS:
173 ret = max77705_battery_get_status(fuelgauge, &val->intval);
174 break;
175 case POWER_SUPPLY_PROP_PRESENT:
176 ret = max77705_fg_check_battery_present(fuelgauge, &val->intval);
177 break;
178 case POWER_SUPPLY_PROP_VOLTAGE_NOW:
179 ret = max77705_fg_read_reg(fuelgauge, VCELL_REG, &val->intval);
180 break;
181 case POWER_SUPPLY_PROP_VOLTAGE_OCV:
182 ret = max77705_fg_read_reg(fuelgauge, VFOCV_REG, &val->intval);
183 break;
184 case POWER_SUPPLY_PROP_VOLTAGE_AVG:
185 ret = max77705_fg_read_reg(fuelgauge, AVR_VCELL_REG, &val->intval);
186 break;
187 case POWER_SUPPLY_PROP_CURRENT_NOW:
188 ret = max77705_fg_read_reg(fuelgauge, CURRENT_REG, &val->intval);
189 break;
190 case POWER_SUPPLY_PROP_CURRENT_AVG:
191 ret = max77705_fg_read_reg(fuelgauge, AVG_CURRENT_REG, &val->intval);
192 break;
193 case POWER_SUPPLY_PROP_CHARGE_NOW:
194 ret = max77705_fg_read_reg(fuelgauge, REMCAP_REP_REG, &val->intval);
195 break;
196 case POWER_SUPPLY_PROP_CHARGE_FULL:
197 ret = max77705_fg_read_reg(fuelgauge, FULLCAP_REP_REG, &val->intval);
198 break;
199 case POWER_SUPPLY_PROP_CHARGE_FULL_DESIGN:
200 ret = max77705_fg_read_reg(fuelgauge, DESIGNCAP_REG, &val->intval);
201 break;
202 case POWER_SUPPLY_PROP_CAPACITY:
203 ret = max77705_fg_read_reg(fuelgauge, SOCREP_REG, &val->intval);
204 break;
205 case POWER_SUPPLY_PROP_TEMP:
206 ret = max77705_fg_read_temp(fuelgauge, &val->intval);
207 break;
208 case POWER_SUPPLY_PROP_TIME_TO_EMPTY_NOW:
209 ret = max77705_fg_read_reg(fuelgauge, TIME_TO_EMPTY_REG, &val->intval);
210 break;
211 case POWER_SUPPLY_PROP_TIME_TO_FULL_NOW:
212 ret = max77705_fg_read_reg(fuelgauge, TIME_TO_FULL_REG, &val->intval);
213 break;
214 case POWER_SUPPLY_PROP_CYCLE_COUNT:
215 ret = max77705_fg_read_reg(fuelgauge, CYCLES_REG, &val->intval);
216 break;
217 case POWER_SUPPLY_PROP_MODEL_NAME:
218 val->strval = max77705_fuelgauge_model;
219 break;
> 220 case POWER_SUPPLY_PROP_MANUFACTURER:
221 val->strval = max77705_fuelgauge_manufacturer;
222 break;
223 default:
224 return -EINVAL;
225 }
226
227 if (ret)
228 return ret;
229
230 max77705_unit_adjustment(fuelgauge, psp, val);
231
232 return 0;
233 }
234
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-10-10 20:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 15:55 [PATCH v6 0/7] Add support for Maxim Integrated MAX77705 MFD Dzmitry Sankouski
2024-10-07 15:55 ` [PATCH v6 1/7] power: supply: add undervoltage health status property Dzmitry Sankouski
2024-10-07 15:55 ` [PATCH v6 2/7] dt-bindings: mfd: add maxim,max77705 Dzmitry Sankouski
2024-10-07 20:07 ` Rob Herring (Arm)
2024-10-07 15:55 ` [PATCH v6 3/7] mfd: Add new driver for MAX77705 PMIC Dzmitry Sankouski
2024-10-15 14:02 ` Lee Jones
2024-10-21 15:04 ` Dzmitry Sankouski
2024-10-25 8:57 ` Lee Jones
2024-10-22 8:37 ` Dzmitry Sankouski
2024-10-07 15:55 ` [PATCH v6 4/7] input: max77693: add max77705 haptic support Dzmitry Sankouski
2024-10-07 15:55 ` [PATCH v6 5/7] power: supply: max77705: Add charger driver for Maxim 77705 Dzmitry Sankouski
2024-10-16 9:24 ` Uwe Kleine-König
2024-10-07 15:55 ` [PATCH v6 6/7] power: supply: max77705: Add fuel gauge " Dzmitry Sankouski
2024-10-10 20:45 ` kernel test robot [this message]
2024-10-11 11:34 ` kernel test robot
2024-10-11 19:23 ` kernel test robot
2024-10-07 15:55 ` [PATCH v6 7/7] leds: max77705: Add LEDs support Dzmitry Sankouski
2024-10-15 14:33 ` Lee Jones
2024-10-22 15:00 ` Dzmitry Sankouski
2024-10-25 8:55 ` Lee Jones
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=202410110404.etzjIhE5-lkp@intel.com \
--to=lkp@intel.com \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dsankouski@gmail.com \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pavel@ucw.cz \
--cc=robh@kernel.org \
--cc=sre@kernel.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 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).