diff options
| author | Yicong Yang <yangyicong@hisilicon.com> | 2024-03-05 20:25:17 +0800 |
|---|---|---|
| committer | Will Deacon <will@kernel.org> | 2024-03-05 13:42:30 +0000 |
| commit | b037e40a6af2b056f7f15d9aabe7e9a9a7149ff3 (patch) | |
| tree | c5778d402a530db0828ebc4f98c6376fbf7f4da8 /Documentation/admin-guide | |
| parent | f0dbc6d0de38df42184776aa8564c12ceb6f1d61 (diff) | |
| download | linux-stable-b037e40a6af2b056f7f15d9aabe7e9a9a7149ff3.tar.gz linux-stable-b037e40a6af2b056f7f15d9aabe7e9a9a7149ff3.tar.bz2 linux-stable-b037e40a6af2b056f7f15d9aabe7e9a9a7149ff3.zip | |
docs: perf: Fix build warning of hisi-pcie-pmu.rst
`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>
Link: https://lore.kernel.org/r/20240305122517.12179-1-yangyicong@huawei.com
Signed-off-by: Will Deacon <will@kernel.org>
Diffstat (limited to 'Documentation/admin-guide')
| -rw-r--r-- | Documentation/admin-guide/perf/hisi-pcie-pmu.rst | 1 |
1 files changed, 1 insertions, 0 deletions
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". |