From: Shaokun Zhang <zhangshaokun@hisilicon.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Will Deacon <will@kernel.org>
Cc: Qi Liu <liuqi115@huawei.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the arm-perf tree
Date: Fri, 26 Mar 2021 17:07:41 +0800 [thread overview]
Message-ID: <c39fe821-3eee-9f2a-3539-6a1f2f415414@hisilicon.com> (raw)
In-Reply-To: <20210326195240.7b937560@canb.auug.org.au>
Hi Will & Stephen,
Apologies for the mistake.
Will, shall I send a new version v5 to fix this issue or other?
Thanks,
Shaokun
On 2021/3/26 16:52, Stephen Rothwell wrote:
> Hi all,
>
> After merging the arm-perf tree, today's linux-next build (htmldocs)
> produced these warnings:
>
> Documentation/admin-guide/perf/hisi-pmu.rst:61: WARNING: Unexpected indentation.
> Documentation/admin-guide/perf/hisi-pmu.rst:62: WARNING: Block quote ends without a blank line; unexpected unindent.
> Documentation/admin-guide/perf/hisi-pmu.rst:69: WARNING: Unexpected indentation.
> Documentation/admin-guide/perf/hisi-pmu.rst:70: WARNING: Block quote ends without a blank line; unexpected unindent.
> Documentation/admin-guide/perf/hisi-pmu.rst:83: WARNING: Unexpected indentation.
>
> Introduced by commit
>
> 9b86b1b41e0f ("docs: perf: Add new description on HiSilicon uncore PMU v2")
>
next prev parent reply other threads:[~2021-03-26 9:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 8:52 linux-next: build warnings after merge of the arm-perf tree Stephen Rothwell
2021-03-26 9:07 ` Shaokun Zhang [this message]
2021-03-29 8:47 ` Will Deacon
2021-03-29 9:06 ` liuqi (BA)
2021-03-29 10:06 ` Will Deacon
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=c39fe821-3eee-9f2a-3539-6a1f2f415414@hisilicon.com \
--to=zhangshaokun@hisilicon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=liuqi115@huawei.com \
--cc=sfr@canb.auug.org.au \
--cc=will@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 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).