public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Peng Ma <peng.ma@nxp.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: drivers/rtc/rtc-fsl-ftm-alarm.c:310:36: warning: 'ftm_imx_acpi_ids' defined but not used
Date: Tue, 3 Dec 2024 16:42:35 +0800	[thread overview]
Message-ID: <202412031620.1tzCLuCU-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   cdd30ebb1b9f36159d66f088b61aee264e649d7a
commit: 929a3270488956316214d70cd4e2ba3fa56ffe31 rtc: fsl-ftm-alarm: enable acpi support
date:   4 years, 8 months ago
config: arm-randconfig-004-20240106 (https://download.01.org/0day-ci/archive/20241203/202412031620.1tzCLuCU-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241203/202412031620.1tzCLuCU-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/202412031620.1tzCLuCU-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/rtc/rtc-fsl-ftm-alarm.c:310:36: warning: 'ftm_imx_acpi_ids' defined but not used [-Wunused-const-variable=]
     310 | static const struct acpi_device_id ftm_imx_acpi_ids[] = {
         |                                    ^~~~~~~~~~~~~~~~


vim +/ftm_imx_acpi_ids +310 drivers/rtc/rtc-fsl-ftm-alarm.c

   309	
 > 310	static const struct acpi_device_id ftm_imx_acpi_ids[] = {
   311		{"NXP0011",},
   312		{ }
   313	};
   314	MODULE_DEVICE_TABLE(acpi, ftm_imx_acpi_ids);
   315	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2024-12-03  8:43 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=202412031620.1tzCLuCU-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=peng.ma@nxp.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