From: Mark Pearson <markpearson@lenovo.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Jonathan Corbet <corbet@lwn.net>,
Hans de Goede <hdegoede@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: [External] linux-next: build failure after merge of the pm tree
Date: Wed, 9 Dec 2020 08:56:31 -0500 [thread overview]
Message-ID: <203934b6-dd68-b02d-757f-c0336352d397@lenovo.com> (raw)
In-Reply-To: <20201209205754.41ac2424@canb.auug.org.au>
On 09/12/2020 04:57, Stephen Rothwell wrote:
> Hi all,
>
> After merging the pm tree, today's linux-next build (htmldocs) failed
> like this:
>
> Sphinx parallel build error:
> docutils.utils.SystemMessage: /home/sfr/next/next/Documentation/ABI/testing/sysfs-platform_profile.rst:1: (SEVERE/4) Missing matching underline for section title overline.
>
> =======================================================================
> Platform Profile Selection (e.g. :ref:`\/sys\/firmware\/acpi\/platform_profile <abi_sys_firmware_acpi_platform_profile>`)
>
> Caused by commit
>
> ff950bebd0e0 ("Documentation: Add documentation for new platform_profile sysfs attribute")
>
My apologies - I hadn't run the 'make htmldocs' command so I missed this
one.
I've been able to reproduce the error and fix the error. I do see:
WARNING: document isn't included in any toctree
but I think this is benign - I believe I'm getting it just because I
converted the file to .rst (as requested by Andy Shevchenko). If this is
important and needs to be addressed urgently as well let me know.
Rafael - I want to run a couple more sanity tests and will push the
update for this (with the other fixes for the platform_profile.c code)
for review later today.
Thanks
Mark
next prev parent reply other threads:[~2020-12-09 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 9:57 linux-next: build failure after merge of the pm tree Stephen Rothwell
2020-12-09 13:56 ` Mark Pearson [this message]
2020-12-09 14:33 ` [External] " Jonathan Corbet
2020-12-09 15:04 ` Mark Pearson
2020-12-10 0:24 ` Jonathan Corbet
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=203934b6-dd68-b02d-757f-c0336352d397@lenovo.com \
--to=markpearson@lenovo.com \
--cc=corbet@lwn.net \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sfr@canb.auug.org.au \
/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).