From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Kees Cook <keescook@chromium•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build warnings after merge of the kspp tree
Date: Mon, 5 Feb 2024 16:14:46 +1100 [thread overview]
Message-ID: <20240205161446.4b0c90fb@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
Hi all,
After merging the kspp tree, today's linux-next build (htmldocs) produced
these warnings:
include/linux/overflow.h:97: warning: Function parameter or struct member 'var' not described in 'inc_wrap'
include/linux/overflow.h:97: warning: Function parameter or struct member 'offset' not described in 'inc_wrap'
include/linux/overflow.h:97: warning: Excess function parameter 'a' description in 'inc_wrap'
include/linux/overflow.h:97: warning: Excess function parameter 'b' description in 'inc_wrap'
include/linux/overflow.h:142: warning: Function parameter or struct member 'var' not described in 'dec_wrap'
include/linux/overflow.h:142: warning: Function parameter or struct member 'offset' not described in 'dec_wrap'
include/linux/overflow.h:142: warning: Excess function parameter 'a' description in 'dec_wrap'
include/linux/overflow.h:142: warning: Excess function parameter 'b' description in 'dec_wrap'
Introduced by commit
6ad835d8849c ("overflow: Introduce inc_wrap() and dec_wrap()")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-02-05 5:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 5:14 Stephen Rothwell [this message]
2024-02-05 12:43 ` linux-next: build warnings after merge of the kspp tree Kees Cook
-- strict thread matches above, loose matches on Subject: below --
2021-08-26 8:00 Stephen Rothwell
2021-08-27 3:29 ` Kees Cook
2016-06-22 5:14 Stephen Rothwell
2016-06-22 17:10 ` Kees Cook
2016-06-22 17:39 ` Kees Cook
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=20240205161446.4b0c90fb@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=keescook@chromium$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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