From: kernel test robot <lkp@intel.com>
To: Shree Ramamoorthy <s-ramamoorthy@ti.com>,
lgirdwood@gmail.com, broonie@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, aaro.koskinen@iki.fi,
andreas@kemnade.info, khilman@baylibre.com, rogerq@kernel.org,
tony@atomide.com, jerome.neanne@baylibre.com,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, m-leonard@ti.com, praneeth@ti.com,
christophe.jaillet@wanadoo.fr
Subject: Re: [PATCH v2 4/7] regulator: tps65215: Add chip_data struct for multi-PMIC support
Date: Sat, 4 Jan 2025 17:53:09 +0800 [thread overview]
Message-ID: <202501041724.qQwuHm5z-lkp@intel.com> (raw)
In-Reply-To: <20250103230446.197597-5-s-ramamoorthy@ti.com>
Hi Shree,
kernel test robot noticed the following build errors:
[auto build test ERROR on broonie-regulator/for-next]
[also build test ERROR on next-20241220]
[cannot apply to robh/for-next tmlind-omap/for-next linus/master v6.13-rc5]
[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/Shree-Ramamoorthy/regulator-dt-bindings-Add-TI-TPS65215-PMIC-bindings/20250104-070914
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
patch link: https://lore.kernel.org/r/20250103230446.197597-5-s-ramamoorthy%40ti.com
patch subject: [PATCH v2 4/7] regulator: tps65215: Add chip_data struct for multi-PMIC support
config: i386-buildonly-randconfig-004-20250104 (https://download.01.org/0day-ci/archive/20250104/202501041724.qQwuHm5z-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250104/202501041724.qQwuHm5z-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/202501041724.qQwuHm5z-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/regulator/tps65219-regulator.c:266:44: error: 'TPS65215_LDO_2' undeclared here (not in a function); did you mean 'TPS65219_LDO_2'?
266 | TPS65219_REGULATOR("LDO2", "ldo2", TPS65215_LDO_2,
| ^~~~~~~~~~~~~~
drivers/regulator/tps65219-regulator.c:104:43: note: in definition of macro 'TPS65219_REGULATOR'
104 | .id = _id, \
| ^~~
drivers/regulator/tps65219-regulator.c:268:28: error: 'TPS65215_REG_LDO2_VOUT' undeclared here (not in a function); did you mean 'TPS65219_REG_LDO2_VOUT'?
268 | TPS65215_REG_LDO2_VOUT,
| ^~~~~~~~~~~~~~~~~~~~~~
drivers/regulator/tps65219-regulator.c:109:43: note: in definition of macro 'TPS65219_REGULATOR'
109 | .vsel_reg = _vr, \
| ^~~
drivers/regulator/tps65219-regulator.c:271:28: error: 'TPS65215_ENABLE_LDO2_EN_MASK' undeclared here (not in a function); did you mean 'TPS65219_ENABLE_LDO2_EN_MASK'?
271 | TPS65215_ENABLE_LDO2_EN_MASK, 0, 0, tps65215_ldo_2_range,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/regulator/tps65219-regulator.c:116:43: note: in definition of macro 'TPS65219_REGULATOR'
116 | .enable_mask = _em, \
| ^~~
>> drivers/regulator/tps65219-regulator.c:330:10: error: 'TPS65215' undeclared here (not in a function); did you mean 'TPS65219'?
330 | [TPS65215] = {
| ^~~~~~~~
| TPS65219
>> drivers/regulator/tps65219-regulator.c:330:10: error: array index in initializer not of integer type
drivers/regulator/tps65219-regulator.c:330:10: note: (near initialization for 'chip_info_table')
In file included from include/linux/kernel.h:16,
from drivers/regulator/tps65219-regulator.c:13:
drivers/regulator/tps65219-regulator.c: In function 'tps65219_regulator_probe':
drivers/regulator/tps65219-regulator.c:365:36: error: 'regulators' undeclared (first use in this function); did you mean 'regulator'?
365 | for (i = 0; i < ARRAY_SIZE(regulators); i++) {
| ^~~~~~~~~~
include/linux/array_size.h:11:33: note: in definition of macro 'ARRAY_SIZE'
11 | #define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) + __must_be_array(arr))
| ^~~
drivers/regulator/tps65219-regulator.c:365:36: note: each undeclared identifier is reported only once for each function it appears in
365 | for (i = 0; i < ARRAY_SIZE(regulators); i++) {
| ^~~~~~~~~~
include/linux/array_size.h:11:33: note: in definition of macro 'ARRAY_SIZE'
11 | #define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) + __must_be_array(arr))
| ^~~
In file included from include/linux/array_size.h:5:
include/linux/compiler.h:245:77: error: expression in static assertion is not an integer
245 | #define __BUILD_BUG_ON_ZERO_MSG(e, msg) ((int)sizeof(struct {_Static_assert(!(e), msg);}))
| ^
include/linux/compiler.h:249:33: note: in expansion of macro '__BUILD_BUG_ON_ZERO_MSG'
249 | #define __must_be_array(a) __BUILD_BUG_ON_ZERO_MSG(__same_type((a), &(a)[0]), "must be array")
| ^~~~~~~~~~~~~~~~~~~~~~~
include/linux/array_size.h:11:59: note: in expansion of macro '__must_be_array'
11 | #define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) + __must_be_array(arr))
| ^~~~~~~~~~~~~~~
drivers/regulator/tps65219-regulator.c:365:25: note: in expansion of macro 'ARRAY_SIZE'
365 | for (i = 0; i < ARRAY_SIZE(regulators); i++) {
| ^~~~~~~~~~
drivers/regulator/tps65219-regulator.c: At top level:
drivers/regulator/tps65219-regulator.c:329:34: warning: 'chip_info_table' defined but not used [-Wunused-variable]
329 | static struct tps65219_chip_data chip_info_table[] = {
| ^~~~~~~~~~~~~~~
vim +330 drivers/regulator/tps65219-regulator.c
328
329 static struct tps65219_chip_data chip_info_table[] = {
> 330 [TPS65215] = {
331 .rdesc = tps65215_regs,
332 .rdesc_size = ARRAY_SIZE(tps65215_regs),
333 .common_rdesc = common_regs,
334 .common_rdesc_size = ARRAY_SIZE(common_regs),
335 .common_irq_types = common_regulator_irq_types,
336 .common_irq_size = ARRAY_SIZE(common_regulator_irq_types),
337 },
338 [TPS65219] = {
339 .rdesc = tps65219_regs,
340 .rdesc_size = ARRAY_SIZE(tps65219_regs),
341 .common_rdesc = common_regs,
342 .common_rdesc_size = ARRAY_SIZE(common_regs),
343 .common_irq_types = common_regulator_irq_types,
344 .common_irq_size = ARRAY_SIZE(common_regulator_irq_types),
345 .irq_types = tps65219_regulator_irq_types,
346 .dev_irq_size = ARRAY_SIZE(tps65219_regulator_irq_types),
347 },
348 };
349
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-01-04 9:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 23:04 [PATCH v2 0/7] Add TI TPS65215 PMIC Regulator Support Shree Ramamoorthy
2025-01-03 23:04 ` [PATCH v2 1/7] regulator: dt-bindings: Add TI TPS65215 PMIC bindings Shree Ramamoorthy
2025-01-04 10:13 ` Krzysztof Kozlowski
2025-01-06 19:50 ` Shree Ramamoorthy
2025-01-03 23:04 ` [PATCH v2 2/7] regulator: tps65215: Update function & struct names Shree Ramamoorthy
2025-01-04 8:38 ` kernel test robot
2025-01-04 10:37 ` kernel test robot
2025-01-03 23:04 ` [PATCH v2 3/7] regulator: tps65215: Update IRQ structs to include TPS65215 Shree Ramamoorthy
2025-01-03 23:04 ` [PATCH v2 4/7] regulator: tps65215: Add chip_data struct for multi-PMIC support Shree Ramamoorthy
2025-01-04 9:53 ` kernel test robot [this message]
2025-01-03 23:04 ` [PATCH v2 5/7] regulator: tps65215: Update platform_device_id table Shree Ramamoorthy
2025-01-04 10:14 ` Krzysztof Kozlowski
2025-01-07 22:15 ` Shree Ramamoorthy
2025-01-03 23:04 ` [PATCH v2 6/7] regulator: tps65215: Define probe() helper functions Shree Ramamoorthy
2025-01-03 23:04 ` [PATCH v2 7/7] regulator: tps65215: Restructure probe() for multi-PMIC support Shree Ramamoorthy
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=202501041724.qQwuHm5z-lkp@intel.com \
--to=lkp@intel.com \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=broonie@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jerome.neanne@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=m-leonard@ti.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=s-ramamoorthy@ti.com \
--cc=tony@atomide.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®