All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH 00/10] Fix documentation warnings at linux-next
Date: Fri, 15 Jan 2021 13:05:56 +0100	[thread overview]
Message-ID: <CAKXUXMxRp4tRbMi4+P6pW4Zom7vZ0hfAWX47+aQ7nunLmyYpUQ@mail.gmail.com> (raw)
In-Reply-To: <20210115104947.71d99e87@coco.lan>

On Fri, Jan 15, 2021 at 10:49 AM Mauro Carvalho Chehab
<mchehab+huawei@kernel.org> wrote:
>
> Hi Lukas,
>
> Em Fri, 15 Jan 2021 07:12:38 +0100
> Lukas Bulwahn <lukas.bulwahn@gmail.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

  reply	other threads:[~2021-01-15 12:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15  6:12 [PATCH 00/10] Fix documentation warnings at linux-next Lukas Bulwahn
2021-01-15  9:49 ` Mauro Carvalho Chehab
2021-01-15 12:05   ` Lukas Bulwahn [this message]
2021-01-15 12:36     ` Mauro Carvalho Chehab
2021-01-15 12:41       ` Mauro Carvalho Chehab
2021-01-15 13:47   ` Jonathan Cameron
2021-01-17 15:42     ` Jonathan Cameron
2021-01-19  9:17       ` William Breathitt Gray
2021-01-19 10:41         ` Jonathan Cameron
2021-01-19 14:07           ` Fabrice Gasnier
2021-01-15 16:37 ` Jonathan Corbet
  -- strict thread matches above, loose matches on Subject: below --
2021-01-14  7:53 Mauro Carvalho Chehab
2021-01-14  7:53 ` Mauro Carvalho Chehab
2021-01-14  7:53 ` Mauro Carvalho Chehab

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=CAKXUXMxRp4tRbMi4+P6pW4Zom7vZ0hfAWX47+aQ7nunLmyYpUQ@mail.gmail.com \
    --to=lukas.bulwahn@gmail.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    /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.