From: Randy Dunlap <rdunlap@infradead.org>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Linux 5.10-rc2 (docs build)
Date: Mon, 2 Nov 2020 11:23:25 -0800 [thread overview]
Message-ID: <4a538b19-2bfd-5c7c-047c-7ed4292b89c8@infradead.org> (raw)
In-Reply-To: <20201102175922.4ed74e7a@coco.lan>
On 11/2/20 8:59 AM, Mauro Carvalho Chehab wrote:
> Em Mon, 2 Nov 2020 08:02:34 -0800
> Randy Dunlap <rdunlap@infradead.org> escreveu:
>
>> On 11/2/20 12:33 AM, Mauro Carvalho Chehab wrote:
>>> Em Mon, 2 Nov 2020 08:58:41 +0100
>>> Mauro Carvalho Chehab <mchehab@kernel.org> escreveu:
>>>
>>>> Hi Randy,
>>>>
>>>> Em Sun, 1 Nov 2020 16:01:54 -0800
>>>> Randy Dunlap <rdunlap@infradead.org> escreveu:
>>>>
>>>>> Something broke the docs build (SEVERE):
>>>>>
>>>>>
>>>>> Sphinx parallel build error:
>>>>> docutils.utils.SystemMessage: /home/rdunlap/lnx/lnx-510-rc2/Documentation/ABI/testing/sysfs-bus-rapidio:2: (SEVERE/4) Title level inconsistent:
>>>>>
>>>>> Attributes Common for All RapidIO Devices
>>>>> -----------------------------------------
>>>>>
>>>>>
>>>>
>>>> On what tree did you notice this? Linux-next or upstream?
>>
>> See $Subject: 5.10-rc2
>>
>>
>>> Also: on what Sphinx version are you getting it? I'm not
>>> able to reproduce the issue here, neither with Sphinx 2.4.4
>>> nor with Sphinx 3.2.1.
>>
>> That could be one source of the problem: ;)
>>
>> from my docs build:
>>
>> Sphinx version: 1.7.6
>> Warning: It is recommended at least Sphinx version 1.7.9.
>> If you want pdf, you need at least 2.4.4.
>
> Could be... From 1.7.6 to 1.7.9, there were bug fixes ;-)
>
> Also, on Sphinx, they stop maintaining old versions once newer
> stable ones are launched. So, any bug on 1.7.x (up to 3.2.x) will
> remain unfixed[1].
>
> In any case, could you please check if this patch solves the
> issue?
>
> https://lore.kernel.org/lkml/6c62ef5c01d39dee8d891f8390c816d2a889670a.1604312590.git.mchehab+huawei@kernel.org/
Nope, sorry, with that patch applied to v5.10-rc2, I get:
reading sources... [ 93%] userspace-api/media/v4l/pixfmt-y8i .. userspace-api/media/v4l/vidioc-querybuf
reading sources... [ 96%] userspace-api/media/v4l/vidioc-querycap .. vm/transhuge
reading sources... [100%] vm/unevictable-lru .. xtensa/mmu
waiting for workers...
{hangs; enter ^C}
Sphinx parallel build error:
docutils.utils.SystemMessage: /home/rdunlap/lnx/lnx-510-rc2/Documentation/ABI/testing/sysfs-class-led-trigger-pattern.orig:16: (SEVERE/4) Unexpected section title.
--
~Randy
next prev parent reply other threads:[~2020-11-02 19:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 23:04 Linux 5.10-rc2 Linus Torvalds
2020-11-02 0:01 ` Linux 5.10-rc2 (docs build) Randy Dunlap
2020-11-02 7:58 ` Mauro Carvalho Chehab
2020-11-02 8:33 ` Mauro Carvalho Chehab
2020-11-02 16:02 ` Randy Dunlap
2020-11-02 16:59 ` Mauro Carvalho Chehab
2020-11-02 19:23 ` Randy Dunlap [this message]
2020-11-02 20:35 ` Mauro Carvalho Chehab
2020-11-02 20:41 ` Randy Dunlap
2020-11-02 21:59 ` Mauro Carvalho Chehab
2020-11-02 10:32 ` [PATCH 0/5] Some fixes for ABI documentation Mauro Carvalho Chehab
2020-11-02 10:32 ` [PATCH 1/5] docs: ABI: sysfs-driver-dma-ioatdma: what starts with /sys Mauro Carvalho Chehab
2020-11-02 10:32 ` [PATCH 2/5] docs: ABI: sysfs-class-net: fix a typo Mauro Carvalho Chehab
2020-11-02 10:32 ` [PATCH 3/5] docs: leds: index.rst: add a missing file Mauro Carvalho Chehab
2020-11-02 10:32 ` [PATCH 4/5] scripts: get_abi.pl: Don't let ABI files to create subtitles Mauro Carvalho Chehab
2020-11-02 10:32 ` [PATCH 5/5] scripts: get_api.pl: Add sub-titles to ABI output Mauro Carvalho Chehab
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=4a538b19-2bfd-5c7c-047c-7ed4292b89c8@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@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;
as well as URLs for NNTP newsgroup(s).