From: kernel test robot <lkp@intel.com>
To: Andreas Kemnade <andreas@kemnade.info>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Guenter Roeck <linux@roeck-us.net>
Cc: oe-kbuild-all@lists.linux.dev, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
Andreas Kemnade <andreas@kemnade.info>
Subject: Re: [PATCH 3/3] regulator: Add FP9931/JD9930 driver
Date: Mon, 10 Nov 2025 11:31:51 +0800 [thread overview]
Message-ID: <202511101159.tlofg0Nn-lkp@intel.com> (raw)
In-Reply-To: <20251107-fp9931-submit-v1-3-aa7b79d9abb6@kemnade.info>
Hi Andreas,
kernel test robot noticed the following build warnings:
[auto build test WARNING on dcb6fa37fd7bc9c3d2b066329b0d27dedf8becaa]
url: https://github.com/intel-lab-lkp/linux/commits/Andreas-Kemnade/dt-bindings-vendor-prefixes-Add-Fitipower/20251108-040835
base: dcb6fa37fd7bc9c3d2b066329b0d27dedf8becaa
patch link: https://lore.kernel.org/r/20251107-fp9931-submit-v1-3-aa7b79d9abb6%40kemnade.info
patch subject: [PATCH 3/3] regulator: Add FP9931/JD9930 driver
config: mips-randconfig-r134-20251110 (https://download.01.org/0day-ci/archive/20251110/202511101159.tlofg0Nn-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 93d445cba39f4dd3dcda4fa1433eca825cf8fc09)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251110/202511101159.tlofg0Nn-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/202511101159.tlofg0Nn-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/regulator/fp9931.c:402:18: sparse: sparse: Initializer entry defined twice
drivers/regulator/fp9931.c:409:18: sparse: also defined here
vim +402 drivers/regulator/fp9931.c
398
399 static const struct regulator_desc regulators[] = {
400 {
401 .name = "V3P3",
> 402 .of_match = of_match_ptr("V3P3"),
403 .id = 0,
404 .ops = &fp9931_v3p3ops,
405 .type = REGULATOR_VOLTAGE,
406 .owner = THIS_MODULE,
407 .enable_reg = FP9931_REG_CONTROL_REG1,
408 .enable_mask = BIT(1),
409 .of_match = of_match_ptr("v3p3"),
410 .n_voltages = 1,
411 .min_uV = 3300000
412 },
413 {
414 .name = "VPOSNEG",
415 .of_match = of_match_ptr("VPOSNEG"),
416 .id = 1,
417 .ops = &fp9931_vposneg_ops,
418 .type = REGULATOR_VOLTAGE,
419 .owner = THIS_MODULE,
420 .n_voltages = ARRAY_SIZE(VPOSNEG_table),
421 .vsel_reg = FP9931_REG_VPOSNEG_SETTING,
422 .vsel_mask = 0x3F,
423 .volt_table = VPOSNEG_table,
424 },
425 {
426 .name = "VCOM",
427 .of_match = of_match_ptr("VCOM"),
428 .id = 2,
429 .ops = &fp9931_vcom_ops,
430 .type = REGULATOR_VOLTAGE,
431 .owner = THIS_MODULE,
432 .n_voltages = 255,
433 .min_uV = 0,
434 .uV_step = 5000000 / 255,
435 .vsel_reg = FP9931_REG_VCOM_SETTING,
436 .vsel_mask = 0xFF
437 },
438 };
439
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-11-10 3:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 20:06 [PATCH 0/3] regulator: Add FP9931/JD9930 Andreas Kemnade
2025-11-07 20:06 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add Fitipower Andreas Kemnade
2025-11-08 12:10 ` Krzysztof Kozlowski
2025-11-07 20:06 ` [PATCH 2/3] dt-bindings: regulator: Add Fitipower FP9931/JD9930 Andreas Kemnade
2025-11-08 12:17 ` Krzysztof Kozlowski
2025-11-08 14:21 ` Andreas Kemnade
2025-11-08 14:46 ` Krzysztof Kozlowski
2025-11-08 16:52 ` Andreas Kemnade
2025-11-09 17:13 ` Krzysztof Kozlowski
2025-11-09 21:12 ` Andreas Kemnade
2025-11-10 7:30 ` Krzysztof Kozlowski
2025-11-10 12:28 ` Andreas Kemnade
2025-11-07 20:06 ` [PATCH 3/3] regulator: Add FP9931/JD9930 driver Andreas Kemnade
2025-11-08 12:21 ` Krzysztof Kozlowski
2025-11-08 23:03 ` Andreas Kemnade
2025-11-10 3:31 ` kernel test robot [this message]
2025-11-10 11:29 ` kernel test robot
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=202511101159.tlofg0Nn-lkp@intel.com \
--to=lkp@intel.com \
--cc=andreas@kemnade.info \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@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).