mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>
Subject: Re: [PULL] Docs for 4.13
Date: Tue, 4 Jul 2017 13:24:13 -0600	[thread overview]
Message-ID: <20170704132413.55274d6d@lwn.net> (raw)
In-Reply-To: <CA+55aFxUVMM7HzGccqWk4ByRQAvJ11BN4raL2KL4J7GSXVx-7Q@mail.gmail.com>

On Mon, 3 Jul 2017 21:32:33 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:

> Eg things like
> 
>   Error: Cannot open file ./kernel/rcu/srcu.c
>   Error: Cannot open file ./kernel/rcu/srcu.c
> 
> happen simply because that file no longer exists, and the docs never
> got updated.
> 
> So my merge didn't even try to fix those kinds of things at all.  I
> literally just looked at the conflicts and moved those over to the rst
> files, and that was it. There's a lot of other changes that never
> cause conflicts for the simple reason that those changes never caused
> documentation changes to begin with.
> 
> Now, this is obviously not new, but it does strike me that if checking
> for these kinds of things was easier and part of "make allmodconfig",
> then we might have less of it happen.

I see Markus already tossed out a patch using the sphinx "dummy mode".
It might be possible to create a dead-simple linter for this kind of
thing that would be quite a bit faster, but I wonder how much we really
need it.  Problems like this pop up with great regularity, but they
tend to be caught and fixed fairly quickly.  Meanwhile, the world
stubbornly refuses to end if the docs build tosses out a few (more)
errors for a few days. I don't think we have to slow down everybody's
build for this.

(Getting something into the build-and-boot testers might not be a bad
idea, though).

I've committed a patch to fix this particular problem, will send it
youward in a few days.

jon

  parent reply	other threads:[~2017-07-04 19:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03 13:20 Jonathan Corbet
2017-07-04  4:32 ` Linus Torvalds
2017-07-04  7:56   ` Markus Heiser
2017-07-04 19:24   ` Jonathan Corbet [this message]
2017-07-15  9:04     ` Daniel Vetter

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=20170704132413.55274d6d@lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

Powered by JetHome