public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Steven Rostedt <rostedt@goodmis•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Tom Zanussi <zanussi@kernel•org>,
	Jonathan Corbet <corbet@lwn•net>
Subject: linux-next: build failure after merge of the ftrace tree
Date: Wed, 3 Jun 2020 17:42:53 +1000	[thread overview]
Message-ID: <20200603174253.60deace5@canb.auug.org.au> (raw)

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

Hi all,

After merging the ftrace tree, today's linux-next build (htmldocs)
failed like this:


Sphinx parallel build error:
docutils.utils.SystemMessage: /home/sfr/next/next/Documentation/trace/histogram-design.rst:219: (SEVERE/4) Unexpected section title.

.
.

Caused by commit

  16b585fe7192 ("tracing: Add histogram-design document")

I am running a slightly out of date version os sphynx (2.4.3) ...

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2020-06-03  7:43 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03  7:42 Stephen Rothwell [this message]
2020-06-03 15:10 ` linux-next: build failure after merge of the ftrace tree Tom Zanussi
2020-06-03 15:22 ` Steven Rostedt
2020-06-03 15:24   ` Tom Zanussi
2020-06-03 15:30     ` Steven Rostedt
2020-06-03 21:49       ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2025-11-06  1:33 Stephen Rothwell
2025-11-06  2:01 ` Steven Rostedt
2025-10-02 15:50 Mark Brown
2025-10-06  0:31 ` Masami Hiramatsu
2025-03-11  5:27 Stephen Rothwell
2025-03-11 13:22 ` Steven Rostedt
2024-11-08  4:21 Stephen Rothwell
2024-11-08 14:59 ` Steven Rostedt
2024-11-08 15:09   ` Alice Ryhl
2024-11-08 20:35     ` Steven Rostedt
2024-11-08 21:05       ` Miguel Ojeda
2024-11-08 21:53         ` Miguel Ojeda
2024-11-09 11:09           ` Steven Rostedt
2024-11-09 11:55             ` Miguel Ojeda
2024-11-09 13:03               ` Steven Rostedt
2024-11-09 16:57                 ` Miguel Ojeda
2024-11-06  3:04 Stephen Rothwell
2024-11-06 15:02 ` Steven Rostedt
2024-11-06 17:47   ` Linus Torvalds
2024-11-20 23:27 ` Stephen Rothwell
2024-10-10  2:46 Stephen Rothwell
2024-10-10  3:13 ` Donglin Peng
2024-10-10 13:27 ` Steven Rostedt
2024-10-10 14:08   ` Donglin Peng
2024-10-10 15:04     ` Steven Rostedt
2024-10-10 15:58     ` Steven Rostedt
2023-10-23  2:30 Stephen Rothwell
2023-10-23  3:32 ` Matthew Wilcox
2023-10-23 13:41   ` Steven Rostedt
2023-10-26  1:18 ` Stephen Rothwell
2023-10-26  1:21   ` Steven Rostedt
2022-01-12  0:31 Stephen Rothwell
2022-01-14  1:02 ` Stephen Rothwell
2022-01-14  1:04   ` Steven Rostedt
2022-01-14  2:16   ` Steven Rostedt
2022-01-14  2:58     ` Stephen Rothwell
2022-01-14  3:02       ` Stephen Rothwell
2022-01-14  3:25         ` Steven Rostedt
2022-01-14  3:34           ` Stephen Rothwell
2022-01-14  3:50             ` Steven Rostedt
2022-01-14  5:12               ` Yinan Liu
2022-01-14  6:42               ` Stephen Rothwell
2021-06-10  8:08 Stephen Rothwell
2021-06-10  8:26 ` Peter Zijlstra
2021-06-10 15:06   ` Steven Rostedt
2021-06-15  6:51     ` Mark-PK Tsai
2014-11-21  7:32 Stephen Rothwell
2014-11-21 10:50 ` Jiri Kosina
2014-11-21 14:20   ` Steven Rostedt
2014-11-21 14:23     ` Jiri Kosina
2014-11-21 14:27     ` Steven Rostedt
2014-11-21 12:43 ` Steven Rostedt
2013-03-01  2:47 Stephen Rothwell
2013-03-01  3:06 ` Steven Rostedt
2013-03-02  2:45 ` Steven Rostedt
2013-03-02  3:42   ` Stephen Rothwell
2013-03-02  3:55     ` Steven Rostedt
2013-03-02  4:17       ` Stephen Rothwell
2013-03-02  4:22         ` Steven Rostedt
2013-03-02  4:55           ` Stephen Rothwell

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=20200603174253.60deace5@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=corbet@lwn$(echo .)net \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=rostedt@goodmis$(echo .)org \
    --cc=zanussi@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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