From: kernel test robot <lkp@intel.com>
To: Sunil V L <sunilvl@ventanamicro.com>
Cc: oe-kbuild-all@lists.linux.dev, Anup Patel <anup@brainfault.org>
Subject: [avpatel:riscv_sbi_sse_v3 28/57] drivers/mailbox/riscv-sbi-mpxy-mbox.c:1005:36: warning: 'mpxy_mbox_acpi_match' defined but not used
Date: Sat, 8 Feb 2025 16:09:57 +0800 [thread overview]
Message-ID: <202502081628.bYgIWGAH-lkp@intel.com> (raw)
tree: https://github.com/avpatel/linux.git riscv_sbi_sse_v3
head: 89fd1a54d40f5fbd0a1c7fb10f51829f13385a9a
commit: 13851aef320d7e43e85b08933a00593dd1322653 [28/57] mailbox/riscv-sbi-mpxy: Add ACPI support
config: riscv-randconfig-001-20250207 (https://download.01.org/0day-ci/archive/20250208/202502081628.bYgIWGAH-lkp@intel.com/config)
compiler: riscv32-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250208/202502081628.bYgIWGAH-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/202502081628.bYgIWGAH-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/mailbox/riscv-sbi-mpxy-mbox.c:1005:36: warning: 'mpxy_mbox_acpi_match' defined but not used [-Wunused-const-variable=]
1005 | static const struct acpi_device_id mpxy_mbox_acpi_match[] = {
| ^~~~~~~~~~~~~~~~~~~~
vim +/mpxy_mbox_acpi_match +1005 drivers/mailbox/riscv-sbi-mpxy-mbox.c
1004
> 1005 static const struct acpi_device_id mpxy_mbox_acpi_match[] = {
1006 { "RSCV0005" },
1007 {}
1008 };
1009 MODULE_DEVICE_TABLE(acpi, mpxy_mbox_acpi_match);
1010
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-08 8:10 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=202502081628.bYgIWGAH-lkp@intel.com \
--to=lkp@intel.com \
--cc=anup@brainfault.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sunilvl@ventanamicro.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 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.