From: Jonathan Corbet <corbet@lwn.net>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: mchehab+huawei@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/10] Fix documentation warnings at linux-next
Date: Fri, 15 Jan 2021 09:37:56 -0700 [thread overview]
Message-ID: <20210115093756.5feaf63c@lwn.net> (raw)
In-Reply-To: <CAKXUXMziQ2H7_oiVSxbt1=bDFkjLQYOiOgd00YGyDnCTVDhbqA@mail.gmail.com>
On Fri, 15 Jan 2021 07:12:38 +0100
Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
> 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?
I'm certainly not going to complain about warning fixes! If you want to
take up this work, all I can say is - I'm looking forward to the patches.
Thanks for doing this.
jon
next prev parent reply other threads:[~2021-01-15 16:38 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
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 [this message]
-- 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=20210115093756.5feaf63c@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--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.