From: Will Deacon <will@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Junhao He <hejunhao3@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 warning after merge of the arm-perf tree
Date: Mon, 19 Jun 2023 11:09:27 +0100 [thread overview]
Message-ID: <20230619100926.GA13483@willie-the-truck> (raw)
In-Reply-To: <20230619143736.39949f20@canb.auug.org.au>
On Mon, Jun 19, 2023 at 02:37:36PM +1000, Stephen Rothwell wrote:
> After merging the arm-perf tree, today's linux-next build (htmldocs)
> produced this warning:
>
> Documentation/admin-guide/perf/hisi-pmu.rst:107: ERROR: Unexpected indentation.
>
> Introduced by commit
>
> ea8d1c062a0e ("docs: perf: Add new description for HiSilicon UC PMU")
Cheers, Stephen. I'll fix this.
Will
next prev parent reply other threads:[~2023-06-19 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 4:37 linux-next: build warning after merge of the arm-perf tree Stephen Rothwell
2023-06-19 10:09 ` Will Deacon [this message]
2023-10-11 6:22 Stephen Rothwell
2023-10-12 8:19 ` Ilkka Koskinen
2023-10-12 11:31 ` Will Deacon
2024-03-05 4:10 Stephen Rothwell
2024-03-05 12:03 ` 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=20230619100926.GA13483@willie-the-truck \
--to=will@kernel.org \
--cc=hejunhao3@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).