linux-kernel - Re: [PATCH 00/10] Fix documentation warnings at linux-next

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: <CAKXUXMxRp4tRbMi4+P6pW4Zom7vZ0hfAWX47+aQ7nunLmyYpUQ@mail.gmail.com>
Date:   Fri, 15 Jan 2021 13:05:56 +0100
From:   Lukas Bulwahn <lukas.bulwahn@...il.com>
To:     Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc:     Jonathan Corbet <corbet@....net>,
        "open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Jonathan Cameron <Jonathan.Cameron@...wei.com>
Subject: Re: [PATCH 00/10] Fix documentation warnings at linux-next

On Fri, Jan 15, 2021 at 10:49 AM Mauro Carvalho Chehab
<mchehab+huawei@...nel.org> wrote:
>
> Hi Lukas,
>
> Em Fri, 15 Jan 2021 07:12:38 +0100
> Lukas Bulwahn <lukas.bulwahn@...il.com> escreveu:
>
> > [reduced the recipient list to the main responsible ones and list]
> >
> > Hi Mauro, hi Jonathan,
> >
> > We both, Mauro and I, have been submitting patches to address the
> > documentation warnings on linux-next. If it is okay with you, Mauro, I
> > would like to take responsibility for the task to send out the patches
> > to address all warnings on linux-next in make htmldocs and follow up
> > with all the discussions. I can also provide a short weekly summary
> > (probably always on Friday) on what is pending where and what I could
> > not resolve by myself.
> >
> > Is that okay for you?
> >
> > If at some point I do not have the time to take care anymore, I will
> > let you know.
>
> Yeah, sure!
>
> Anyway, after applying the patches I sent this week, the warnings
> I'm getting are all due to the validation scripts I wrote. So, if
> everything gets merged (either yours or my version), we'll have zero
> Sphinx/kernel-doc warnings again.
>

It is a never ending story... I already have seen two new warnings on
today's linux-next and sent out patches.

> $ scripts/documentation-file-ref-check
> $ scripts/get_abi.pl validate

I will also try out those two scripts, but I cannot commit to
follow-up on all of those yet. I am also looking into addressing all
kerneldoc warnings, even if not pulled in by make htmldocs.

Lukas