All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [ardb:for-kernelci 2/4] drivers/rtc/rtc-efi.c:151:21: warning: unused variable 'rtc'
Date: Fri, 11 Jul 2025 22:10:05 +0800	[thread overview]
Message-ID: <202507112141.qUTkwckc-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git for-kernelci
head:   2b69cc853cfd5d483e48785735ee845d3bffde85
commit: 1dcb6fdcd10617262528f945a11852fb4aee9197 [2/4] efi-rtc: Remove wakeup functionality
config: arm-randconfig-004-20250711 (https://download.01.org/0day-ci/archive/20250711/202507112141.qUTkwckc-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250711/202507112141.qUTkwckc-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/202507112141.qUTkwckc-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/rtc/rtc-efi.c:151:21: warning: unused variable 'rtc' [-Wunused-variable]
     151 |         struct rtc_device *rtc = dev_get_drvdata(dev);
         |                            ^~~
   1 warning generated.


vim +/rtc +151 drivers/rtc/rtc-efi.c

5e3fd9e5810f14 dann frazier       2009-03-31  146  
501385f2a783c0 Geliang Tang       2015-11-07  147  static int efi_procfs(struct device *dev, struct seq_file *seq)
501385f2a783c0 Geliang Tang       2015-11-07  148  {
1dcb6fdcd10617 Ard Biesheuvel     2025-07-11  149  	efi_time_t        eft;
501385f2a783c0 Geliang Tang       2015-11-07  150  	efi_time_cap_t    cap;
101ca8d05913b7 Shanker Donthineni 2023-01-02 @151  	struct rtc_device *rtc = dev_get_drvdata(dev);
501385f2a783c0 Geliang Tang       2015-11-07  152  
501385f2a783c0 Geliang Tang       2015-11-07  153  	memset(&eft, 0, sizeof(eft));
501385f2a783c0 Geliang Tang       2015-11-07  154  	memset(&cap, 0, sizeof(cap));
501385f2a783c0 Geliang Tang       2015-11-07  155  
501385f2a783c0 Geliang Tang       2015-11-07  156  	efi.get_time(&eft, &cap);
501385f2a783c0 Geliang Tang       2015-11-07  157  
501385f2a783c0 Geliang Tang       2015-11-07  158  	seq_printf(seq,
501385f2a783c0 Geliang Tang       2015-11-07  159  		   "Time\t\t: %u:%u:%u.%09u\n"
501385f2a783c0 Geliang Tang       2015-11-07  160  		   "Date\t\t: %u-%u-%u\n"
501385f2a783c0 Geliang Tang       2015-11-07  161  		   "Daylight\t: %u\n",
501385f2a783c0 Geliang Tang       2015-11-07  162  		   eft.hour, eft.minute, eft.second, eft.nanosecond,
501385f2a783c0 Geliang Tang       2015-11-07  163  		   eft.year, eft.month, eft.day,
501385f2a783c0 Geliang Tang       2015-11-07  164  		   eft.daylight);
501385f2a783c0 Geliang Tang       2015-11-07  165  
501385f2a783c0 Geliang Tang       2015-11-07  166  	if (eft.timezone == EFI_UNSPECIFIED_TIMEZONE)
501385f2a783c0 Geliang Tang       2015-11-07  167  		seq_puts(seq, "Timezone\t: unspecified\n");
501385f2a783c0 Geliang Tang       2015-11-07  168  	else
501385f2a783c0 Geliang Tang       2015-11-07  169  		/* XXX fixme: convert to string? */
501385f2a783c0 Geliang Tang       2015-11-07  170  		seq_printf(seq, "Timezone\t: %u\n", eft.timezone);
501385f2a783c0 Geliang Tang       2015-11-07  171  
501385f2a783c0 Geliang Tang       2015-11-07  172  	/*
501385f2a783c0 Geliang Tang       2015-11-07  173  	 * now prints the capabilities
501385f2a783c0 Geliang Tang       2015-11-07  174  	 */
501385f2a783c0 Geliang Tang       2015-11-07  175  	seq_printf(seq,
501385f2a783c0 Geliang Tang       2015-11-07  176  		   "Resolution\t: %u\n"
501385f2a783c0 Geliang Tang       2015-11-07  177  		   "Accuracy\t: %u\n"
501385f2a783c0 Geliang Tang       2015-11-07  178  		   "SetstoZero\t: %u\n",
501385f2a783c0 Geliang Tang       2015-11-07  179  		   cap.resolution, cap.accuracy, cap.sets_to_zero);
501385f2a783c0 Geliang Tang       2015-11-07  180  
501385f2a783c0 Geliang Tang       2015-11-07  181  	return 0;
501385f2a783c0 Geliang Tang       2015-11-07  182  }
501385f2a783c0 Geliang Tang       2015-11-07  183  

:::::: The code at line 151 was first introduced by commit
:::::: 101ca8d05913b7d1e6e8b9dd792193d4082fff86 rtc: efi: Enable SET/GET WAKEUP services as optional

:::::: TO: Shanker Donthineni <sdonthineni@nvidia.com>
:::::: CC: Alexandre Belloni <alexandre.belloni@bootlin.com>

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

                 reply	other threads:[~2025-07-11 14: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=202507112141.qUTkwckc-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ardb@kernel.org \
    --cc=llvm@lists.linux.dev \
    --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.