From: kernel test robot <lkp@intel.com>
To: "Ricardo B. Marliere" <ricardo@marliere.net>
Cc: oe-kbuild-all@lists.linux.dev,
Sebastian Reichel <sebastian.reichel@collabora.com>
Subject: [sre-power-supply:for-next 58/60] drivers/power/supply/power_supply.h:25:37: warning: 'power_supply_attr_group' defined but not used
Date: Sat, 2 Mar 2024 15:58:08 +0800 [thread overview]
Message-ID: <202403021518.SUQzk3oA-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git for-next
head: 71c2cc5cbf686c2397f43cbcb51a31589bdcee7b
commit: ea4367c40c79a5f16cb0de8a94a6b72697d37f06 [58/60] power: supply: core: move power_supply_attr_group into #ifdef block
config: um-randconfig-001-20240301 (https://download.01.org/0day-ci/archive/20240302/202403021518.SUQzk3oA-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/20240302/202403021518.SUQzk3oA-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/202403021518.SUQzk3oA-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/power/supply/power_supply_leds.c:18:
>> drivers/power/supply/power_supply.h:25:37: warning: 'power_supply_attr_group' defined but not used [-Wunused-const-variable=]
25 | static const struct attribute_group power_supply_attr_group;
| ^~~~~~~~~~~~~~~~~~~~~~~
vim +/power_supply_attr_group +25 drivers/power/supply/power_supply.h
23
24 static inline void power_supply_init_attrs(void) {}
> 25 static const struct attribute_group power_supply_attr_group;
26 #define power_supply_uevent NULL
27
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-03-02 7:59 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=202403021518.SUQzk3oA-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ricardo@marliere.net \
--cc=sebastian.reichel@collabora.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;
as well as URLs for NNTP newsgroup(s).