linux-kernel - Re: linux-next: build warnings after merge of the vfs-brauner tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAGudoHE-3MNRSCMX0tf-t-Exopvw4n5M8b2SFZcbbiM7is-gkw@mail.gmail.com>
Date: Wed, 12 Nov 2025 11:57:25 +0100
From: Mateusz Guzik <mjguzik@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Christian Brauner <brauner@...nel.org>, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, 
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warnings after merge of the vfs-brauner tree

On Wed, Nov 12, 2025 at 11:55 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi Mateusz,
>
> On Wed, 12 Nov 2025 11:10:59 +0100 Mateusz Guzik <mjguzik@...il.com> wrote:
> >
> > That func is a little special and I would argue it should not have
> > these documented. Is there a way to exempt it?
>
> Since the function is declared static, it doesn't really need
> kernel-doc, so you should start the comment with "/*" instead of "/**".
>

Perfect, thanks.

It is Christian's call though.