From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
LKML <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [GIT PULL] Documentation for 5.10
Date: Tue, 13 Oct 2020 12:21:08 +0200 [thread overview]
Message-ID: <20201013122108.232a57d6@coco.lan> (raw)
In-Reply-To: <20201013205856.21f762ff@canb.auug.org.au>
Em Tue, 13 Oct 2020 20:58:56 +1100
Stephen Rothwell <sfr@canb.auug.org.au> escreveu:
> Hi Mauro,
>
> On Tue, 13 Oct 2020 10:49:50 +0200 Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> >
> > If everything goes well on tomorrow's next, I'll send you a pull request
> > with those.
>
> Sorry, bad timing, but there won't be a linux-next tomorrow (I have a
> day off).
No problem. I'll then do it on Thursday. Enjoy your day off!
>
> > The other ones depend on merges from DRM, hwmon and other
> > trees. So, I'll keep rebasing them and should be sending you a late
> > PR by the end of the merge window, fixing the remaining doc issues.
> >
> > We're aiming to have zero documentation warnings by
> > the end of the merge window, when built with Sphinx 2.x,
>
> That would be nice. I am still getting about 35-40 each day.
Yeah, currently the warnings are so polluted that it is hard
for developers to see new ones.
Btw, after rebasing the remaining fixes on today's next, there
are a few new warnings:
build succeeded, 7 warnings.
Hopefully this will be solved soon, after we merge those
fixes upstream, as it will make easier to detect new
ones early and should help maintainers to enforce a cleaner
build.
Thanks,
Mauro
prev parent reply other threads:[~2020-10-13 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 19:30 [GIT PULL] Documentation for 5.10 Jonathan Corbet
2020-10-12 23:50 ` pr-tracker-bot
2020-10-13 8:49 ` Mauro Carvalho Chehab
2020-10-13 9:58 ` Stephen Rothwell
2020-10-13 10:21 ` Mauro Carvalho Chehab [this message]
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=20201013122108.232a57d6@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).