From: kernel test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: oe-kbuild-all@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, arm@kernel.org
Subject: [soc:board-remove-7.3 170/294] drivers/rtc/rtc-stm32.c:795:13: warning: 'stm32_rtc_clear_events' defined but not used
Date: Thu, 10 Sep 2026 17:40:58 +0200 [thread overview]
Message-ID: <202609100500.VDsB697w-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git board-remove-7.3
head: 3ac93c1e700558259ea604f7d4f37e26820fba15
commit: 99ab6d2408a83752e16a39683a743c131f3d5cb3 [170/294] rtc: stm32: remove mcu support
config: sparc-allyesconfig (https://download.01.org/0day-ci/archive/20260910/202609100500.VDsB697w-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260910/202609100500.VDsB697w-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/202609100500.VDsB697w-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/rtc/rtc-stm32.c:795:13: warning: 'stm32_rtc_clear_events' defined but not used [-Wunused-function]
795 | static void stm32_rtc_clear_events(struct stm32_rtc *rtc,
| ^~~~~~~~~~~~~~~~~~~~~~
vim +/stm32_rtc_clear_events +795 drivers/rtc/rtc-stm32.c
4e64350f42e2ce Amelie Delaunay 2017-01-11 794
02b0cc345c2a1b Amelie Delaunay 2018-05-17 @795 static void stm32_rtc_clear_events(struct stm32_rtc *rtc,
02b0cc345c2a1b Amelie Delaunay 2018-05-17 796 unsigned int flags)
02b0cc345c2a1b Amelie Delaunay 2018-05-17 797 {
02b0cc345c2a1b Amelie Delaunay 2018-05-17 798 const struct stm32_rtc_registers *regs = &rtc->data->regs;
02b0cc345c2a1b Amelie Delaunay 2018-05-17 799
02b0cc345c2a1b Amelie Delaunay 2018-05-17 800 /* Flags are cleared by writing 0 in RTC_ISR */
02b0cc345c2a1b Amelie Delaunay 2018-05-17 801 writel_relaxed(readl_relaxed(rtc->base + regs->isr) & ~flags,
02b0cc345c2a1b Amelie Delaunay 2018-05-17 802 rtc->base + regs->isr);
02b0cc345c2a1b Amelie Delaunay 2018-05-17 803 }
02b0cc345c2a1b Amelie Delaunay 2018-05-17 804
:::::: The code at line 795 was first introduced by commit
:::::: 02b0cc345c2a1b7f1c590796a02d84e49e51ded0 rtc: stm32: rework register management to prepare other version of RTC
:::::: TO: Amelie Delaunay <amelie.delaunay@st.com>
:::::: CC: Alexandre Belloni <alexandre.belloni@bootlin.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-10 15:41 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=202609100500.VDsB697w-lkp@intel.com \
--to=lkp@intel.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox