[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YxnfZSeYzPCJzIp9@leoy-huanghe.lan>
Date: Thu, 8 Sep 2022 20:27:31 +0800
From: Leo Yan <leo.yan@...aro.org>
To: kernel test robot <lkp@...el.com>
Cc: carsten.haitzler@...s.arm.com, linux-kernel@...r.kernel.org,
kbuild-all@...ts.01.org, coresight@...ts.linaro.org,
suzuki.poulose@....com, mathieu.poirier@...aro.org,
mike.leach@...aro.org, linux-perf-users@...r.kernel.org,
acme@...nel.org
Subject: Re: [PATCH v8 13/13] perf test: Add relevant documentation about
CoreSight testing
On Wed, Sep 07, 2022 at 10:59:55AM +0800, kernel test robot wrote:
[...]
> All warnings (new ones prefixed by >>):
Thanks for reporting!
> >> Documentation/trace/coresight/coresight-perf.rst:102: WARNING: Inline emphasis start-string without end-string.
>
> vim +102 Documentation/trace/coresight/coresight-perf.rst
>
> 96
> 97 CoreSight / ASM Pure Loop
> 98 CoreSight / Memcpy 16k 10 Threads
> 99 CoreSight / Thread Loop 10 Threads - Check TID
> 100 etc.
> 101
> > 102 These perf record tests will not run if the tool binaries do not exist
> 103 in tests/shell/coresight/*/ and will be skipped. If you do not have
> 104 CoreSight support in hardware then either do not build perf with
> 105 CoreSight support or remove these binaries in order to not have these
> 106 tests fail and have them skip instead.
> 107
Hi Carsten,
Just note that I reproduced the warning at my side; after I used the
escape for '*' like below, the warning can be dismissed.
tests/shell/coresight/\*/
Thanks,
Leo
Powered by blists - more mailing lists