mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	LKML <linux-kernel@vger.kernel.org>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	Matthew Wilcox <willy@infradead.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [GIT PULL] Docs-build warning fixes for 5.10-rc3
Date: Thu, 5 Nov 2020 09:06:52 +1100	[thread overview]
Message-ID: <20201105090652.003eb7bf@canb.auug.org.au> (raw)
In-Reply-To: <CAHk-=wghhw0SpqSKKUqt5eum=UfLD3Qa0suoRxLy_cJc4hChug@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]

Hi Linus,

On Tue, 3 Nov 2020 13:18:27 -0800 Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> On Tue, Nov 3, 2020 at 11:44 AM Jonathan Corbet <corbet@lwn.net> wrote:
> >
> > This pull contains a series of warning fixes from Mauro; once applied, the
> > number of warnings from the once-noisy docs build process is nearly zero.
> > Getting to this point has required a lot of work; once there, hopefully we
> > can keep things that way.  
> 
> I wonder if it is quiet enough that we could make new doc build noise
> trigger some kind of linux-next warning?
> 
> I know Stephen was at least looking at doc build warnings justding by
> the thread a couple of weeks ago.

What I am currently doing is a "make htmldocs" on your tree and then again
on the whole linux-next release and reporting changes.

There is currently one message produced in your tree (after I add all
the "pending fixes") and I have reported that this morning.  So things
are looking pretty good now - a lot of good work over the past couple
of releases.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2020-11-04 22:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03 19:44 Jonathan Corbet
2020-11-03 21:18 ` Linus Torvalds
2020-11-03 21:24   ` Matthew Wilcox
2020-11-04 22:06   ` Stephen Rothwell [this message]
2020-11-04 22:40     ` Jonathan Corbet
2020-11-03 21:51 ` pr-tracker-bot

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=20201105090652.003eb7bf@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=willy@infradead.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

all inboxes | Powered by JetHome®