Received-SPF: pass (google.com: domain of linux-kernel+bounces-92358-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
CC: <hejunhao3@huawei.com>, <yangyicong@hisilicon.com>
Subject: Re: [PATCH -next] drivers/perf: hisi: Fix build warning of
 hisi-pcie-pmu.rst
From: Yicong Yang <yangyicong@huawei.com>
To: <will@kernel.org>, <sfr@canb.auug.org.au>, <linux-kernel@vger.kernel.org>,
	<linux-next@vger.kernel.org>
References: <20240305121003.4497-1-yangyicong@huawei.com>
Message-ID: <071459df-223a-516f-2300-f013e3ddc1c9@huawei.com>
Date: Tue, 5 Mar 2024 20:24:17 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.5.1
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <20240305121003.4497-1-yangyicong@huawei.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

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@hisilicon.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@hisilicon.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".
>