From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android11-kiwi-5.4 458/458] drivers/of/unittest.c:131:31: warning: 'unittest_gpio_driver' defined but not used
Date: Mon, 22 Dec 2025 21:28:23 +0800 [thread overview]
Message-ID: <202512222151.17DigM2T-lkp@intel.com> (raw)
Hi Frank,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android11-kiwi-5.4
head: 8cc11e1aa30fd981a8d5bd390a4352c37dfe543e
commit: f6997a2416b028f369af5b859e4115fa6f56e4d5 [458/458] of: unittest: add overlay gpio test to catch gpio hog problem
config: arm64-randconfig-r073-20251216 (https://download.01.org/0day-ci/archive/20251222/202512222151.17DigM2T-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251222/202512222151.17DigM2T-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/202512222151.17DigM2T-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/of/unittest.c:131:31: warning: 'unittest_gpio_driver' defined but not used [-Wunused-variable]
131 | static struct platform_driver unittest_gpio_driver = {
| ^~~~~~~~~~~~~~~~~~~~
vim +/unittest_gpio_driver +131 drivers/of/unittest.c
130
> 131 static struct platform_driver unittest_gpio_driver = {
132 .probe = unittest_gpio_probe,
133 .remove = unittest_gpio_remove,
134 .driver = {
135 .name = "unittest-gpio",
136 .of_match_table = of_match_ptr(unittest_gpio_id),
137 },
138 };
139
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-22 13:29 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=202512222151.17DigM2T-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--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 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.