| Message ID | a7a4fe3295b543d361541fd5f1c6fadc9e255dec.1622898327.git.mchehab+huawei@kernel.org (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | docs: avoid using ReST :doc:`foo` tag | expand |
On Sat, Jun 05, 2021 at 03:18:29PM +0200, Mauro Carvalho Chehab wrote: > The :doc:`foo` tag is auto-generated via automarkup.py. > So, use the filename at the sources, instead of :doc:`foo`. > > Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> > --- > Documentation/trace/coresight/coresight.rst | 8 +++++--- > 1 file changed, 5 insertions(+), 3 deletions(-) > Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org> > diff --git a/Documentation/trace/coresight/coresight.rst b/Documentation/trace/coresight/coresight.rst > index 169749efd8d1..1ec8dc35b1d8 100644 > --- a/Documentation/trace/coresight/coresight.rst > +++ b/Documentation/trace/coresight/coresight.rst > @@ -315,7 +315,8 @@ intermediate links as required. > > Note: ``cti_sys0`` appears in two of the connections lists above. > CTIs can connect to multiple devices and are arranged in a star topology > -via the CTM. See (:doc:`coresight-ect`) [#fourth]_ for further details. > +via the CTM. See (Documentation/trace/coresight/coresight-ect.rst) > +[#fourth]_ for further details. > Looking at this device we see 4 connections:: > > linaro-developer:~# ls -l /sys/bus/coresight/devices/cti_sys0/connections > @@ -606,7 +607,8 @@ interface provided for that purpose by the generic STM API:: > crw------- 1 root root 10, 61 Jan 3 18:11 /dev/stm0 > root@genericarmv8:~# > > -Details on how to use the generic STM API can be found here:- :doc:`../stm` [#second]_. > +Details on how to use the generic STM API can be found here: > +- Documentation/trace/stm.rst [#second]_. > > The CTI & CTM Modules > --------------------- > @@ -616,7 +618,7 @@ individual CTIs and components, and can propagate these between all CTIs via > channels on the CTM (Cross Trigger Matrix). > > A separate documentation file is provided to explain the use of these devices. > -(:doc:`coresight-ect`) [#fourth]_. > +(Documentation/trace/coresight/coresight-ect.rst) [#fourth]_. > > > .. [#first] Documentation/ABI/testing/sysfs-bus-coresight-devices-stm > -- > 2.31.1 >
diff --git a/Documentation/trace/coresight/coresight.rst b/Documentation/trace/coresight/coresight.rst index 169749efd8d1..1ec8dc35b1d8 100644 --- a/Documentation/trace/coresight/coresight.rst +++ b/Documentation/trace/coresight/coresight.rst @@ -315,7 +315,8 @@ intermediate links as required. Note: ``cti_sys0`` appears in two of the connections lists above. CTIs can connect to multiple devices and are arranged in a star topology -via the CTM. See (:doc:`coresight-ect`) [#fourth]_ for further details. +via the CTM. See (Documentation/trace/coresight/coresight-ect.rst) +[#fourth]_ for further details. Looking at this device we see 4 connections:: linaro-developer:~# ls -l /sys/bus/coresight/devices/cti_sys0/connections @@ -606,7 +607,8 @@ interface provided for that purpose by the generic STM API:: crw------- 1 root root 10, 61 Jan 3 18:11 /dev/stm0 root@genericarmv8:~# -Details on how to use the generic STM API can be found here:- :doc:`../stm` [#second]_. +Details on how to use the generic STM API can be found here: +- Documentation/trace/stm.rst [#second]_. The CTI & CTM Modules --------------------- @@ -616,7 +618,7 @@ individual CTIs and components, and can propagate these between all CTIs via channels on the CTM (Cross Trigger Matrix). A separate documentation file is provided to explain the use of these devices. -(:doc:`coresight-ect`) [#fourth]_. +(Documentation/trace/coresight/coresight-ect.rst) [#fourth]_. .. [#first] Documentation/ABI/testing/sysfs-bus-coresight-devices-stm
The :doc:`foo` tag is auto-generated via automarkup.py. So, use the filename at the sources, instead of :doc:`foo`. Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> --- Documentation/trace/coresight/coresight.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-)