From: Kees Cook <keescook@chromium.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the kspp tree
Date: Mon, 5 Feb 2024 04:43:50 -0800 [thread overview]
Message-ID: <202402050443.D1A3D9676@keescook> (raw)
In-Reply-To: <20240205161446.4b0c90fb@canb.auug.org.au>
On Mon, Feb 05, 2024 at 04:14:46PM +1100, Stephen Rothwell wrote:
> 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()")
Eek, thanks! I've fixed and pushed this now.
--
Kees Cook
next prev parent reply other threads:[~2024-02-05 12:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 5:14 linux-next: build warnings after merge of the kspp tree Stephen Rothwell
2024-02-05 12:43 ` Kees Cook [this message]
-- 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=202402050443.D1A3D9676@keescook \
--to=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).