All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: Re: [PATCH V6 2/5] mfd: bq257xx: Add support for BQ25703A core driver
Date: Thu, 14 Aug 2025 08:34:48 +0800	[thread overview]
Message-ID: <202508140839.hYfIB0Da-lkp@intel.com> (raw)

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20250812214300.123129-3-macroalpha82@gmail.com>
References: <20250812214300.123129-3-macroalpha82@gmail.com>
TO: Chris Morgan <macroalpha82@gmail.com>
TO: linux-rockchip@lists.infradead.org
CC: linux-pm@vger.kernel.org
CC: devicetree@vger.kernel.org
CC: broonie@kernel.org
CC: lee@kernel.org
CC: lgirdwood@gmail.com
CC: sre@kernel.org
CC: heiko@sntech.de
CC: conor+dt@kernel.org
CC: krzk+dt@kernel.org
CC: robh@kernel.org
CC: Chris Morgan <macromorgan@hotmail.com>

Hi Chris,

kernel test robot noticed the following build warnings:

[auto build test WARNING on broonie-regulator/for-next]
[also build test WARNING on sre-power-supply/for-next rockchip/for-next linus/master v6.17-rc1 next-20250813]
[cannot apply to lee-mfd/for-mfd-next lee-mfd/for-mfd-fixes]
[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/Chris-Morgan/dt-bindings-mfd-ti-bq25703a-Add-TI-BQ25703A-Charger/20250813-054704
base:   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
patch link:    https://lore.kernel.org/r/20250812214300.123129-3-macroalpha82%40gmail.com
patch subject: [PATCH V6 2/5] mfd: bq257xx: Add support for BQ25703A core driver
:::::: branch date: 26 hours ago
:::::: commit date: 26 hours ago
config: m68k-randconfig-r073-20250814 (https://download.01.org/0day-ci/archive/20250814/202508140839.hYfIB0Da-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 15.1.0

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>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202508140839.hYfIB0Da-lkp@intel.com/

New smatch warnings:
drivers/mfd/bq257xx.c:46 bq257xx_probe() warn: sizeof(NUMBER)?

Old smatch warnings:
drivers/mfd/bq257xx.c:47 bq257xx_probe() warn: sizeof(NUMBER)?

vim +46 drivers/mfd/bq257xx.c

4b63b1500e4b18 Chris Morgan 2025-08-12  41  
4b63b1500e4b18 Chris Morgan 2025-08-12  42  static int bq257xx_probe(struct i2c_client *client)
4b63b1500e4b18 Chris Morgan 2025-08-12  43  {
4b63b1500e4b18 Chris Morgan 2025-08-12  44  	struct bq257xx_device *ddata;
4b63b1500e4b18 Chris Morgan 2025-08-12  45  	static const struct mfd_cell cells[] = {
4b63b1500e4b18 Chris Morgan 2025-08-12 @46  		MFD_CELL_NAME("bq257xx-regulator"),
4b63b1500e4b18 Chris Morgan 2025-08-12  47  		MFD_CELL_NAME("bq257xx-charger"),
4b63b1500e4b18 Chris Morgan 2025-08-12  48  	};
4b63b1500e4b18 Chris Morgan 2025-08-12  49  	int ret;
4b63b1500e4b18 Chris Morgan 2025-08-12  50  
4b63b1500e4b18 Chris Morgan 2025-08-12  51  	ddata = devm_kzalloc(&client->dev, sizeof(*ddata), GFP_KERNEL);
4b63b1500e4b18 Chris Morgan 2025-08-12  52  	if (!ddata)
4b63b1500e4b18 Chris Morgan 2025-08-12  53  		return -ENOMEM;
4b63b1500e4b18 Chris Morgan 2025-08-12  54  
4b63b1500e4b18 Chris Morgan 2025-08-12  55  	ddata->client = client;
4b63b1500e4b18 Chris Morgan 2025-08-12  56  	ddata->regmap = devm_regmap_init_i2c(client, &bq25703_regmap_config);
4b63b1500e4b18 Chris Morgan 2025-08-12  57  	if (IS_ERR(ddata->regmap)) {
4b63b1500e4b18 Chris Morgan 2025-08-12  58  		return dev_err_probe(&client->dev, PTR_ERR(ddata->regmap),
4b63b1500e4b18 Chris Morgan 2025-08-12  59  				     "Failed to allocate register map\n");
4b63b1500e4b18 Chris Morgan 2025-08-12  60  	}
4b63b1500e4b18 Chris Morgan 2025-08-12  61  
4b63b1500e4b18 Chris Morgan 2025-08-12  62  	i2c_set_clientdata(client, ddata);
4b63b1500e4b18 Chris Morgan 2025-08-12  63  
4b63b1500e4b18 Chris Morgan 2025-08-12  64  	ret = devm_mfd_add_devices(&client->dev, PLATFORM_DEVID_AUTO,
4b63b1500e4b18 Chris Morgan 2025-08-12  65  				   cells, ARRAY_SIZE(cells), NULL, 0, NULL);
4b63b1500e4b18 Chris Morgan 2025-08-12  66  	if (ret)
4b63b1500e4b18 Chris Morgan 2025-08-12  67  		return dev_err_probe(&client->dev, ret,
4b63b1500e4b18 Chris Morgan 2025-08-12  68  				     "Failed to register child devices\n");
4b63b1500e4b18 Chris Morgan 2025-08-12  69  
4b63b1500e4b18 Chris Morgan 2025-08-12  70  	return ret;
4b63b1500e4b18 Chris Morgan 2025-08-12  71  }
4b63b1500e4b18 Chris Morgan 2025-08-12  72  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2025-08-14  0:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14  0:34 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-12 21:42 [PATCH V6 0/5] Add Texas Instruments BQ25703A Charger Chris Morgan
2025-08-12 21:42 ` [PATCH V6 2/5] mfd: bq257xx: Add support for BQ25703A core driver Chris Morgan
2025-08-12 21:42   ` Chris Morgan

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=202508140839.hYfIB0Da-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=error27@gmail.com \
    --cc=oe-kbuild@lists.linux.dev \
    /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.