[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200911075035.326f91b3@coco.lan>
Date: Fri, 11 Sep 2020 07:50:35 +0200
From: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
To: Jonathan Corbet <corbet@....net>
Cc: Linux Doc Mailing List <linux-doc@...r.kernel.org>,
linux-kernel@...r.kernel.org,
Christian König <christian.koenig@....com>,
"David S. Miller" <davem@...emloft.net>,
Andy Gross <agross@...nel.org>,
Benson Leung <bleung@...omium.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Brendan Higgins <brendanhiggins@...gle.com>,
Cheng-Yi Chiang <cychiang@...omium.org>,
Daniel Vetter <daniel@...ll.ch>,
David Airlie <airlied@...ux.ie>,
Enric Balletbo i Serra <enric.balletbo@...labora.com>,
Guenter Roeck <linux@...ck-us.net>,
Ingo Molnar <mingo@...hat.com>,
Jakub Kicinski <kuba@...nel.org>,
Jean Delvare <jdelvare@...e.com>, Jens Axboe <axboe@...nel.dk>,
Joerg Reuter <jreuter@...na.de>,
Jonathan Cameron <jic23@...nel.org>,
Jyri Sarha <jsarha@...com>, Lee Jones <lee.jones@...aro.org>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Sumit Semwal <sumit.semwal@...aro.org>,
Thierry Reding <thierry.reding@...il.com>,
Thomas Zimmermann <tzimmermann@...e.de>,
Will Deacon <will@...nel.org>
Subject: Re: [PATCH 00/30] docs: fix documentation build parsing errors
Em Thu, 10 Sep 2020 10:42:50 -0600
Jonathan Corbet <corbet@....net> escreveu:
> On Wed, 9 Sep 2020 16:10:31 +0200
> Mauro Carvalho Chehab <mchehab+huawei@...nel.org> wrote:
>
> > Currently, there are several warnings/errors produced when building
> > the documentation with "make htmldocs".
> >
> > This series fixes almost all such errors. It is produced against
> > linux-next, branch next-20200909.
> >
> > Some of the patches here were already sent individually, but nobody
> > picked them. So, I'm re-sending the full series.
>
> I'd sure love to just apply the whole series and clean up a lot of this
> stuff, but (1) I'm not entirely comfortable taking a few through
> docs-next, and (2) some of them don't apply even if I catch up to -rc4.
> So I'm going to pass through them individually and snag as many as I can...
Yeah. As I commented on the other series, as warnings reach upstream
from different trees, the only sane way to fix them is by using linux-next.
I'll keep rebase those. This way, if something ends being lost, we could
submit upstream by the end of the merge window.
Btw, as Andrii gently submitted a fix for the two remaining litmus doc
warnings, once everything gets merged, htmldocs should now produce
zero doc warnings.
I'll keep track on this. Hopefully, we can make 5.10 free of doc warnings,
and build robots can start warning about newly introduced ones.
Thanks,
Mauro
Powered by blists - more mailing lists