linux-kernel - Re: [PATCH] linux/pipe_fs_i.h: fix kernel-doc warnings after @wait was split

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <0ce3caf2-9209-0968-e78a-f8e067a78ca0@infradead.org>
Date:   Wed, 12 Feb 2020 13:36:02 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Al Viro <viro@...iv.linux.org.uk>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] linux/pipe_fs_i.h: fix kernel-doc warnings after @wait
 was split

On 2/12/20 11:57 AM, Linus Torvalds wrote:
> On Sun, Feb 9, 2020 at 7:36 PM Randy Dunlap <rdunlap@...radead.org> wrote:
>>
>> Fix kernel-doc warnings in struct pipe_inode_info after @wait was
>> split into @rd_wait and @wr_wait.
> 
> Thanks, applied.
> 
> I've considered adding some doc building to my basic tests, but it is
> (a) somewhat slow and (b) has always been very noisy.
> 
> And that (b) is why I really don't do it. The reason I require the
> basic build to be warning-free is that because that way any new
> warnings stand out. But that's just not the case for docs.
> 
> What do you use to notice new errors? Or is there some trick to make
> it less noisy?

It's awfully noisy.  I just do lots of "grep -v" to ignore some messages
that are always there and then I manually ignore lots of others that are
not new.  Very little automation.  No magic tricks.

-- 
~Randy