From: "Ernst, Justin" <justin.ernst@hpe.com>
To: Borislav Petkov <bp@suse.de>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"Travis, Mike" <mike.travis@hpe.com>
Subject: RE: linux-next: build warnings after merge of the tip tree
Date: Mon, 30 Nov 2020 21:56:27 +0000 [thread overview]
Message-ID: <AT5PR8401MB1300D1F5019C5C489BB20E9887F50@AT5PR8401MB1300.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20201130101733.GA6586@zn.tnic>
> On Mon, Nov 30, 2020 at 06:05:03PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the tip tree, today's linux-next build (htmldocs) produced
> > these warnings:
> >
> > Documentation/ABI/testing/sysfs-firmware-sgi_uv:2: WARNING: Unexpected indentation.
> > Documentation/ABI/testing/sysfs-firmware-sgi_uv:2: WARNING: Unexpected indentation.
> > Documentation/ABI/testing/sysfs-firmware-sgi_uv:2: WARNING: Unexpected indentation.
> >
> > Introduced by commit
> >
> > 7ac2f1017115 ("x86/platform/uv: Update ABI documentation of /sys/firmware/sgi_uv/")
>
> Yah, I can reproduce but I have no clue what sphinx wants from me. Line
> 2 looks ok which could mean that the warning line it points to is bogus.
>
> Justin, this is all yours. :)
After scratching my head for a while, I found that the issue was missing empty lines before three different code-block sections.
The line number is definitely bogus, but I wasn't able to discover why.
You can find my patch at: https://lkml.org/lkml/2020/11/30/1196
The patch depends on the v2 patch set Mike Travis <mike.travis@hpe.com> submitted, which hasn't made it to tip yet.
Thanks,
-Justin
>
> Thx.
>
> --
> Regards/Gruss,
> Boris.
>
> SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next prev parent reply other threads:[~2020-11-30 21:58 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 7:05 linux-next: build warnings after merge of the tip tree Stephen Rothwell
2020-11-30 10:17 ` Borislav Petkov
2020-11-30 21:56 ` Ernst, Justin [this message]
2020-11-30 22:18 ` Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2024-02-02 3:59 Stephen Rothwell
2023-12-01 0:29 Stephen Rothwell
2023-12-01 12:09 ` Uros Bizjak
2023-12-04 4:08 ` Stephen Rothwell
2023-12-04 7:02 ` Uros Bizjak
2023-12-11 5:19 ` Stephen Rothwell
2023-12-11 7:06 ` Uros Bizjak
2023-06-02 3:12 Stephen Rothwell
2022-11-21 7:41 Stephen Rothwell
2022-05-20 7:49 Stephen Rothwell
2022-04-27 0:10 Stephen Rothwell
2022-04-27 11:31 ` Borislav Petkov
2022-04-27 13:43 ` Tom Lendacky
2022-03-22 3:51 Stephen Rothwell
2022-03-22 21:52 ` Peter Zijlstra
2022-03-22 23:11 ` Stephen Rothwell
2022-03-21 3:03 Stephen Rothwell
2022-03-21 12:55 ` Peter Zijlstra
2022-03-21 13:04 ` Peter Zijlstra
2022-03-21 13:08 ` Peter Zijlstra
2022-03-21 13:45 ` Peter Zijlstra
2022-03-21 14:19 ` Mark Rutland
2022-03-21 15:28 ` Peter Zijlstra
2022-03-21 15:45 ` Peter Zijlstra
2022-03-21 16:37 ` Linus Torvalds
2022-03-21 16:44 ` Peter Zijlstra
2022-03-21 16:52 ` Linus Torvalds
2022-03-21 22:05 ` Stephen Rothwell
2022-03-21 22:12 ` Alexei Starovoitov
2022-03-21 22:46 ` Stephen Rothwell
2022-03-21 22:50 ` Alexei Starovoitov
2022-03-21 22:55 ` Steven Rostedt
2022-03-22 4:51 ` Masami Hiramatsu
2022-03-22 4:53 ` Alexei Starovoitov
2022-03-22 7:42 ` Peter Zijlstra
2022-03-22 4:38 ` Masami Hiramatsu
2022-03-21 15:28 ` Steven Rostedt
2022-03-21 16:04 ` Peter Zijlstra
2022-03-21 16:12 ` Steven Rostedt
2022-03-21 16:15 ` Steven Rostedt
2022-03-21 16:22 ` Steven Rostedt
2022-03-21 16:39 ` Steven Rostedt
2022-03-21 16:40 ` Peter Zijlstra
2022-03-21 16:45 ` Steven Rostedt
2022-03-21 16:50 ` Peter Zijlstra
2022-03-21 16:54 ` Steven Rostedt
2022-03-22 7:54 ` Peter Zijlstra
2022-03-22 13:12 ` Steven Rostedt
2022-03-22 14:35 ` Peter Zijlstra
2022-03-22 15:04 ` Steven Rostedt
2022-03-22 15:19 ` Peter Zijlstra
2022-03-22 15:48 ` Peter Zijlstra
2022-03-22 16:17 ` Steven Rostedt
2022-03-23 2:23 ` Masami Hiramatsu
2022-03-23 2:42 ` Steven Rostedt
2022-03-23 6:28 ` Masami Hiramatsu
2022-03-22 14:25 ` Masami Hiramatsu
2022-03-21 16:48 ` Peter Zijlstra
2022-03-22 5:31 ` Masami Hiramatsu
2022-03-22 8:08 ` Peter Zijlstra
2022-03-22 9:14 ` Masami Hiramatsu
2022-03-22 12:07 ` Peter Zijlstra
2022-03-22 12:17 ` Peter Zijlstra
2022-03-22 12:46 ` Masami Hiramatsu
2022-03-22 13:22 ` Steven Rostedt
2022-03-22 13:15 ` Mark Rutland
2022-03-22 13:51 ` Masami Hiramatsu
2022-03-22 10:46 ` Peter Zijlstra
2022-03-22 10:59 ` Peter Zijlstra
2021-12-17 3:40 Stephen Rothwell
2022-01-21 23:58 ` Stephen Rothwell
2022-03-15 2:32 ` Stephen Rothwell
2022-04-04 3:26 ` Stephen Rothwell
2021-10-12 10:20 Stephen Rothwell
2021-10-12 13:58 ` André Almeida
2020-11-23 7:19 Stephen Rothwell
2020-11-23 23:03 ` Jarkko Sakkinen
2017-11-02 2:53 Stephen Rothwell
2017-11-03 21:00 ` Masami Hiramatsu
2017-11-04 8:01 ` Ingo Molnar
2017-11-04 12:16 ` Masami Hiramatsu
2017-11-13 11:31 ` Stephen Rothwell
2017-06-23 4:19 Stephen Rothwell
2016-07-14 3:49 Stephen Rothwell
2016-07-14 3:37 Stephen Rothwell
2016-07-14 4:18 ` Stephen Rothwell
2012-10-12 5:11 Stephen Rothwell
2011-01-31 4:27 Stephen Rothwell
2011-01-31 5:08 ` Jaswinder Singh
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=AT5PR8401MB1300D1F5019C5C489BB20E9887F50@AT5PR8401MB1300.NAMPRD84.PROD.OUTLOOK.COM \
--to=justin.ernst@hpe.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mike.travis@hpe.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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).