From: kernel test robot <lkp@intel.com>
To: Alina Yu <alina_yu@richtek.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Mark Brown <broonie@kernel.org>
Subject: [linux-next:master 9961/10967] drivers/regulator/rtq2208-regulator.c:223:35: warning: unused variable 'rtq2208_regulator_ldo_ops'
Date: Fri, 3 May 2024 18:19:16 +0800 [thread overview]
Message-ID: <202405031834.7qPvHF00-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 9221b2819b8a4196eecf5476d66201be60fbcf29
commit: 38bcec0e7cbbd6566c12ae4f2b7a48bd50cd215c [9961/10967] regulator: rtq2208: Fix LDO discharge register and add vsel setting
config: i386-buildonly-randconfig-001-20240503 (https://download.01.org/0day-ci/archive/20240503/202405031834.7qPvHF00-lkp@intel.com/config)
compiler: clang version 18.1.4 (https://github.com/llvm/llvm-project e6c3289804a67ea0bb6a86fadbe454dd93b8d855)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240503/202405031834.7qPvHF00-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/202405031834.7qPvHF00-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/regulator/rtq2208-regulator.c:223:35: warning: unused variable 'rtq2208_regulator_ldo_ops' [-Wunused-const-variable]
223 | static const struct regulator_ops rtq2208_regulator_ldo_ops = {
| ^~~~~~~~~~~~~~~~~~~~~~~~~
1 warning generated.
vim +/rtq2208_regulator_ldo_ops +223 drivers/regulator/rtq2208-regulator.c
85a11f55621a0c Alina Yu 2023-08-07 222
85a11f55621a0c Alina Yu 2023-08-07 @223 static const struct regulator_ops rtq2208_regulator_ldo_ops = {
85a11f55621a0c Alina Yu 2023-08-07 224 .enable = regulator_enable_regmap,
85a11f55621a0c Alina Yu 2023-08-07 225 .disable = regulator_disable_regmap,
85a11f55621a0c Alina Yu 2023-08-07 226 .is_enabled = regulator_is_enabled_regmap,
85a11f55621a0c Alina Yu 2023-08-07 227 .set_active_discharge = regulator_set_active_discharge_regmap,
85a11f55621a0c Alina Yu 2023-08-07 228 .set_suspend_enable = rtq2208_set_suspend_enable,
85a11f55621a0c Alina Yu 2023-08-07 229 .set_suspend_disable = rtq2208_set_suspend_disable,
85a11f55621a0c Alina Yu 2023-08-07 230 };
85a11f55621a0c Alina Yu 2023-08-07 231
:::::: The code at line 223 was first introduced by commit
:::::: 85a11f55621a0c18b22b43ab4219450ac1d19386 regulator: rtq2208: Add Richtek RTQ2208 SubPMIC driver
:::::: TO: Alina Yu <alina_yu@richtek.com>
:::::: CC: Mark Brown <broonie@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-03 10:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202405031834.7qPvHF00-lkp@intel.com \
--to=lkp@intel.com \
--cc=alina_yu@richtek.com \
--cc=broonie@kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).