linux-kernel - Re: [PATCH -next] drivers/perf: hisi: Fix build warning of hisi-pcie-pmu.rst

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Tue, 5 Mar 2024 20:24:17 +0800
From: Yicong Yang <yangyicong@...wei.com>
To: <will@...nel.org>, <sfr@...b.auug.org.au>, <linux-kernel@...r.kernel.org>,
	<linux-next@...r.kernel.org>
CC: <hejunhao3@...wei.com>, <yangyicong@...ilicon.com>
Subject: Re: [PATCH -next] drivers/perf: hisi: Fix build warning of
 hisi-pcie-pmu.rst

The subject should be:

docs: perf: hisi: Fix build warning of hisi-pcie-pmu.rst

Will get this fixed. Sorry for the mistake.

On 2024/3/5 20:10, Yicong Yang wrote:
> From: Yicong Yang <yangyicong@...ilicon.com>
> 
> `make htmldocs SPHINXDIRS="admin-guide"` shows below warnings:
> Documentation/admin-guide/perf/hisi-pcie-pmu.rst:48: ERROR: Unexpected indentation.
> Documentation/admin-guide/perf/hisi-pcie-pmu.rst:49: WARNING: Block quote ends without a blank line; unexpected unindent.
> 
> Fix this.
> 
> Closes: https://lore.kernel.org/lkml/20231011172250.5a6498e5@canb.auug.org.au/
> Fixes: 89a032923d4b ("docs: perf: Update usage for target filter of hisi-pcie-pmu")
> Signed-off-by: Yicong Yang <yangyicong@...ilicon.com>
> ---
>  Documentation/admin-guide/perf/hisi-pcie-pmu.rst | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/admin-guide/perf/hisi-pcie-pmu.rst b/Documentation/admin-guide/perf/hisi-pcie-pmu.rst
> index 678d3865560c..5541ff40e06a 100644
> --- a/Documentation/admin-guide/perf/hisi-pcie-pmu.rst
> +++ b/Documentation/admin-guide/perf/hisi-pcie-pmu.rst
> @@ -44,6 +44,7 @@ The related events usually used to calculate the bandwidth, latency or others.
>  They need to start and end counting at the same time, therefore related events
>  are best used in the same event group to get the expected value. There are two
>  ways to know if they are related events:
> +
>  a) By event name, such as the latency events "xxx_latency, xxx_cnt" or
>     bandwidth events "xxx_flux, xxx_time".
>  b) By event type, such as "event=0xXXXX, event=0x1XXXX".
>