From: Kees Cook <keescook@chromium.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>
Subject: Re: [Regression] Docs build broken by commit 51e46c7a4007
Date: Fri, 21 Feb 2020 14:10:42 -0800 [thread overview]
Message-ID: <202002211406.69D0BAFD@keescook> (raw)
In-Reply-To: <20200221014841.3137229d@lwn.net>
On Fri, Feb 21, 2020 at 01:48:41AM -0700, Jonathan Corbet wrote:
> On Fri, 21 Feb 2020 09:40:01 +0100
> "Rafael J. Wysocki" <rafael@kernel.org> wrote:
>
> > 1.6.5 (I realize that it is older than recommended, but it had been
> > working fine before 5.5-rc1 :-)).
>
> We still intend to support back to 1.4; this version should work.
>
> > I've tried that too, but most often I do something like "make
> > O=../build/somewhere/ htmldocs".
> >
> > But I can do "make O=../build/somewhere/ -j 2 htmldocs" too just fine. :-)
>
> I suspect that the O= plays into this somehow; that's not something I do
> in my own testing. I'll try to take a look at this, but I'm on the road
> and somewhat distracted at the moment...
Ah! Yes, I've not used O= before. I bet it's something weird between the
parallelism detection of a pre-1.7 version and the O=. I'll see if I can
find the problem...
--
Kees Cook
prev parent reply other threads:[~2020-02-21 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 18:50 [Regression] Docs build broken by commit 51e46c7a4007 Rafael J. Wysocki
2020-02-20 20:05 ` Kees Cook
2020-02-20 21:44 ` Rafael J. Wysocki
2020-02-20 22:49 ` Kees Cook
2020-02-21 8:40 ` Rafael J. Wysocki
2020-02-21 8:48 ` Jonathan Corbet
2020-02-21 22:10 ` Kees Cook [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=202002211406.69D0BAFD@keescook \
--to=keescook@chromium.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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.