From: kernel test robot <lkp@intel.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: drivers/rtc/rtc-pl031.c:85: warning: Function parameter or struct member 'range_min' not described in 'pl031_vendor_data'
Date: Mon, 6 Jan 2025 04:05:15 +0800 [thread overview]
Message-ID: <202501060322.FAnXQ5Qy-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: ab75170520d4964f3acf8bb1f91d34cbc650688e
commit: 03f2a0e45f395bc34b0a44105bc7e935bfd40c27 rtc: pl031: set range
date: 4 years, 10 months ago
config: arm-randconfig-r013-20220706 (https://download.01.org/0day-ci/archive/20250106/202501060322.FAnXQ5Qy-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 12.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250106/202501060322.FAnXQ5Qy-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/202501060322.FAnXQ5Qy-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/rtc/rtc-pl031.c:85: warning: Function parameter or struct member 'range_min' not described in 'pl031_vendor_data'
>> drivers/rtc/rtc-pl031.c:85: warning: Function parameter or struct member 'range_max' not described in 'pl031_vendor_data'
vim +85 drivers/rtc/rtc-pl031.c
8ae6e163c1b637 Deepak Saxena 2006-06-25 68
aff05ed5d10352 Linus Walleij 2012-07-30 69 /**
aff05ed5d10352 Linus Walleij 2012-07-30 70 * struct pl031_vendor_data - per-vendor variations
aff05ed5d10352 Linus Walleij 2012-07-30 71 * @ops: the vendor-specific operations used on this silicon version
1bb457fc9268bb Linus Walleij 2012-07-30 72 * @clockwatch: if this is an ST Microelectronics silicon version with a
1bb457fc9268bb Linus Walleij 2012-07-30 73 * clockwatch function
1bb457fc9268bb Linus Walleij 2012-07-30 74 * @st_weekday: if this is an ST Microelectronics silicon version that need
1bb457fc9268bb Linus Walleij 2012-07-30 75 * the weekday fix
559a6fc0508392 Mattias Wallin 2012-07-30 76 * @irqflags: special IRQ flags per variant
aff05ed5d10352 Linus Walleij 2012-07-30 77 */
aff05ed5d10352 Linus Walleij 2012-07-30 78 struct pl031_vendor_data {
aff05ed5d10352 Linus Walleij 2012-07-30 79 struct rtc_class_ops ops;
1bb457fc9268bb Linus Walleij 2012-07-30 80 bool clockwatch;
1bb457fc9268bb Linus Walleij 2012-07-30 81 bool st_weekday;
559a6fc0508392 Mattias Wallin 2012-07-30 82 unsigned long irqflags;
03f2a0e45f395b Alexandre Belloni 2020-03-06 83 time64_t range_min;
03f2a0e45f395b Alexandre Belloni 2020-03-06 84 timeu64_t range_max;
aff05ed5d10352 Linus Walleij 2012-07-30 @85 };
aff05ed5d10352 Linus Walleij 2012-07-30 86
:::::: The code at line 85 was first introduced by commit
:::::: aff05ed5d103524bd69bd9d7b621c5c8a6c63198 rtc: pl031: encapsulate per-vendor ops
:::::: TO: Linus Walleij <linus.walleij@linaro.org>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-01-05 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-05 20:05 kernel test robot [this message]
2025-03-01 2:06 kernel test robot
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=202501060322.FAnXQ5Qy-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®