From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, Fengyan Mu <mufengyan@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-6.6 3124/3124] drivers/ub/ubase/ubase_ubus.c:355:35: warning: unused variable 'ubase_ue_driver'
Date: Sun, 9 Nov 2025 03:48:15 +0800 [thread overview]
Message-ID: <202511090331.elnR753P-lkp@intel.com> (raw)
tree: https://gitee.com/openeuler/kernel.git OLK-6.6
head: 66984acf4b16f28a2cc0d5d6186b4b6bbfd92e26
commit: 727362c0978ca7ecd007ea2f3fc0f7873a615821 [3124/3124] ub: ubase: Support for ELR and entity reset.
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20251109/202511090331.elnR753P-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251109/202511090331.elnR753P-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/202511090331.elnR753P-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/ub/ubase/ubase_ubus.c:355:35: warning: unused variable 'ubase_ue_driver' [-Wunused-const-variable]
355 | static const struct device_driver ubase_ue_driver = {
| ^~~~~~~~~~~~~~~
1 warning generated.
vim +/ubase_ue_driver +355 drivers/ub/ubase/ubase_ubus.c
354
> 355 static const struct device_driver ubase_ue_driver = {
356 .pm = &ubase_ubus_pm_ops,
357 };
358
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-08 19:48 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=202511090331.elnR753P-lkp@intel.com \
--to=lkp@intel.com \
--cc=kernel@openeuler.org \
--cc=mufengyan@huawei.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.