From: kernel test robot <lkp@intel.com>
To: Robert Jones <rjones@gateworks.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: drivers/iio/imu/fxos8700_spi.c:34:36: warning: 'fxos8700_acpi_match' defined but not used
Date: Thu, 23 Nov 2023 15:16:52 +0800 [thread overview]
Message-ID: <202311231427.vEQAuxvI-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 9b6de136b5f0158c60844f85286a593cb70fb364
commit: 84e5ddd5c46ea3bf0cad670da32028994cad5936 iio: imu: Add support for the FXOS8700 IMU
date: 4 years, 1 month ago
config: x86_64-buildonly-randconfig-001-20231012 (https://download.01.org/0day-ci/archive/20231123/202311231427.vEQAuxvI-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/20231123/202311231427.vEQAuxvI-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/202311231427.vEQAuxvI-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/iio/imu/fxos8700_spi.c:34:36: warning: 'fxos8700_acpi_match' defined but not used [-Wunused-const-variable=]
34 | static const struct acpi_device_id fxos8700_acpi_match[] = {
| ^~~~~~~~~~~~~~~~~~~
vim +/fxos8700_acpi_match +34 drivers/iio/imu/fxos8700_spi.c
33
> 34 static const struct acpi_device_id fxos8700_acpi_match[] = {
35 {"FXOS8700", 0},
36 { }
37 };
38 MODULE_DEVICE_TABLE(acpi, fxos8700_acpi_match);
39
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-23 7:17 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=202311231427.vEQAuxvI-lkp@intel.com \
--to=lkp@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rjones@gateworks.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
all inboxes | Powered by JetHome®