linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>
Cc: <hejunhao3@huawei.com>, <yangyicong@hisilicon.com>
Subject: Re: [PATCH -next] drivers/perf: hisi: Fix build warning of hisi-pcie-pmu.rst
Date: Tue, 5 Mar 2024 20:24:17 +0800	[thread overview]
Message-ID: <071459df-223a-516f-2300-f013e3ddc1c9@huawei.com> (raw)
In-Reply-To: <20240305121003.4497-1-yangyicong@huawei.com>

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

      reply	other threads:[~2024-03-05 12:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 12:10 [PATCH -next] drivers/perf: hisi: Fix build warning of hisi-pcie-pmu.rst Yicong Yang
2024-03-05 12:24 ` Yicong Yang [this message]

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=071459df-223a-516f-2300-f013e3ddc1c9@huawei.com \
    --to=yangyicong@huawei.com \
    --cc=hejunhao3@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=will@kernel.org \
    --cc=yangyicong@hisilicon.com \
    /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).