All of lore.kernel.org
 help / color / mirror / Atom feed
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 warning after merge of the kspp tree
Date: Fri, 9 Feb 2024 22:44:08 -0800	[thread overview]
Message-ID: <202402092243.D04BE3C@keescook> (raw)
In-Reply-To: <20240208144842.5491303d@canb.auug.org.au>

On Thu, Feb 08, 2024 at 02:48:42PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the kspp tree, today's linux-next build (htmldocs) produced
> this warning:
> 
> include/linux/string.h:142: warning: Function parameter or struct member 'dst' not described in 'strscpy_pad'
> include/linux/string.h:142: warning: Excess function parameter 'dest' description in 'strscpy_pad'
> include/linux/string.h:142: warning: Excess function parameter 'count' description in 'strscpy_pad'
> 
> Introduced by commit
> 
>   0bf7961afff1 ("string: Allow 2-argument strscpy_pad()")

Thanks! This is fixed now.

-- 
Kees Cook

  reply	other threads:[~2024-02-10  6:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08  3:48 linux-next: build warning after merge of the kspp tree Stephen Rothwell
2024-02-10  6:44 ` Kees Cook [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-09  2:57 Stephen Rothwell
2026-01-09 19:23 ` Kees Cook
2024-03-07  6:16 Stephen Rothwell
2024-03-07 19:25 ` Kees Cook
2024-02-22  5:56 Stephen Rothwell
2021-08-30  8:44 Stephen Rothwell
2021-08-30 23:50 ` Kees Cook
2021-08-31  0:49   ` Stephen Rothwell
2021-09-06  5:41 ` Stephen Rothwell
2021-09-06 17:06   ` Kees Cook
2021-09-06 17:12     ` Linus Torvalds

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=202402092243.D04BE3C@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.