Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Linus Walleij <linus.walleij@linaro.org>
Subject: [linux-next:master 9380/9634] drivers/rtc/rtc-pl031.c:87: warning: Excess struct member 'range_maximum' description in 'pl031_vendor_data'
Date: Fri, 7 Mar 2025 22:42:41 +0800	[thread overview]
Message-ID: <202503072239.fEPJgP3W-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   0a2f889128969dab41861b6e40111aa03dc57014
commit: 6571ef7dc9cfcf04fb858b54c15c1b645d7b2bc6 [9380/9634] rtc: pl031: document struct pl031_vendor_data members
config: arm-randconfig-001-20250307 (https://download.01.org/0day-ci/archive/20250307/202503072239.fEPJgP3W-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project e15545cad8297ec7555f26e5ae74a9f0511203e7)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250307/202503072239.fEPJgP3W-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/202503072239.fEPJgP3W-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/rtc/rtc-pl031.c:87: warning: Function parameter or struct member 'range_max' not described in 'pl031_vendor_data'
>> drivers/rtc/rtc-pl031.c:87: warning: Excess struct member 'range_maximum' description in 'pl031_vendor_data'


vim +87 drivers/rtc/rtc-pl031.c

8ae6e163c1b637e Deepak Saxena     2006-06-25  68  
aff05ed5d103524 Linus Walleij     2012-07-30  69  /**
aff05ed5d103524 Linus Walleij     2012-07-30  70   * struct pl031_vendor_data - per-vendor variations
aff05ed5d103524 Linus Walleij     2012-07-30  71   * @ops: the vendor-specific operations used on this silicon version
1bb457fc9268bb7 Linus Walleij     2012-07-30  72   * @clockwatch: if this is an ST Microelectronics silicon version with a
1bb457fc9268bb7 Linus Walleij     2012-07-30  73   *	clockwatch function
1bb457fc9268bb7 Linus Walleij     2012-07-30  74   * @st_weekday: if this is an ST Microelectronics silicon version that need
1bb457fc9268bb7 Linus Walleij     2012-07-30  75   *	the weekday fix
559a6fc0508392a Mattias Wallin    2012-07-30  76   * @irqflags: special IRQ flags per variant
6571ef7dc9cfcf0 Alexandre Belloni 2025-03-05  77   * @range_min: minimum date/time supported by the RTC
6571ef7dc9cfcf0 Alexandre Belloni 2025-03-05  78   * @range_maximum: maximum date/time supported by the RTC
aff05ed5d103524 Linus Walleij     2012-07-30  79   */
aff05ed5d103524 Linus Walleij     2012-07-30  80  struct pl031_vendor_data {
aff05ed5d103524 Linus Walleij     2012-07-30  81  	struct rtc_class_ops ops;
1bb457fc9268bb7 Linus Walleij     2012-07-30  82  	bool clockwatch;
1bb457fc9268bb7 Linus Walleij     2012-07-30  83  	bool st_weekday;
559a6fc0508392a Mattias Wallin    2012-07-30  84  	unsigned long irqflags;
03f2a0e45f395bc Alexandre Belloni 2020-03-06  85  	time64_t range_min;
03f2a0e45f395bc Alexandre Belloni 2020-03-06  86  	timeu64_t range_max;
aff05ed5d103524 Linus Walleij     2012-07-30 @87  };
aff05ed5d103524 Linus Walleij     2012-07-30  88  

:::::: The code at line 87 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

                 reply	other threads:[~2025-03-07 14:44 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=202503072239.fEPJgP3W-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=linus.walleij@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox