From: kernel test robot <lkp@intel.com>
To: Kees Cook <keescook@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <gustavoars@kernel.org>
Subject: drivers/reset/core.c:64: warning: Excess struct member 'rstc' description in 'reset_control_array'
Date: Fri, 15 Dec 2023 06:19:56 +0800 [thread overview]
Message-ID: <202312150614.kOx8xUkr-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: c7402612e2e61b76177f22e6e7f705adcbecc6fe
commit: fed2ef7abaebe5e0207cd52ae52721ea3da3b5ba reset: Annotate struct reset_control_array with __counted_by
date: 7 weeks ago
config: arm-randconfig-r081-20231214 (https://download.01.org/0day-ci/archive/20231215/202312150614.kOx8xUkr-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/20231215/202312150614.kOx8xUkr-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/202312150614.kOx8xUkr-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/reset/core.c:64: warning: Excess struct member 'rstc' description in 'reset_control_array'
vim +64 drivers/reset/core.c
61fc41317666be Philipp Zabel 2012-11-19 53
17c82e206d2a3c Vivek Gautam 2017-05-22 54 /**
17c82e206d2a3c Vivek Gautam 2017-05-22 55 * struct reset_control_array - an array of reset controls
17c82e206d2a3c Vivek Gautam 2017-05-22 56 * @base: reset control for compatibility with reset control API functions
17c82e206d2a3c Vivek Gautam 2017-05-22 57 * @num_rstcs: number of reset controls
17c82e206d2a3c Vivek Gautam 2017-05-22 58 * @rstc: array of reset controls
17c82e206d2a3c Vivek Gautam 2017-05-22 59 */
17c82e206d2a3c Vivek Gautam 2017-05-22 60 struct reset_control_array {
17c82e206d2a3c Vivek Gautam 2017-05-22 61 struct reset_control base;
17c82e206d2a3c Vivek Gautam 2017-05-22 62 unsigned int num_rstcs;
fed2ef7abaebe5 Kees Cook 2023-09-22 63 struct reset_control *rstc[] __counted_by(num_rstcs);
17c82e206d2a3c Vivek Gautam 2017-05-22 @64 };
17c82e206d2a3c Vivek Gautam 2017-05-22 65
:::::: The code at line 64 was first introduced by commit
:::::: 17c82e206d2a3cd876b64921c59116f1ecdce6ad reset: Add APIs to manage array of resets
:::::: TO: Vivek Gautam <vivek.gautam@codeaurora.org>
:::::: CC: Philipp Zabel <p.zabel@pengutronix.de>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-14 22:20 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=202312150614.kOx8xUkr-lkp@intel.com \
--to=lkp@intel.com \
--cc=gustavoars@kernel.org \
--cc=keescook@chromium.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®