mirrors/linux-stable
1
0
Fork 0
mirror of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git synced 2024-09-25 11:55:37 +00:00
Code Issues Releases Wiki Activity

docs: dev-tools: testing-overview.rst: avoid using ReST :doc:foo markup

Browse source 
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>
Link: https://lore.kernel.org/r/6bbecd4170ee08f36f8060b0719a46c64a21aefc.1623824363.git.mchehab+huawei@kernel.org
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
Mauro Carvalho Chehab 2021-06-16 08:27:24 +02:00 committed by Jonathan Corbet
parent a822b2ee26
commit 3a8b57d27a
1 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
Documentation/dev-tools/testing-overview.rst
View file

@ -71,15 +71,15 @@ can be used to verify that a test is executing particular functions or lines
of code. This is useful for determining how much of the kernel is being tested, of code. This is useful for determining how much of the kernel is being tested,
and for finding corner-cases which are not covered by the appropriate test. and for finding corner-cases which are not covered by the appropriate test.
:doc:`gcov` is GCC's coverage testing tool, which can be used with the kernel Documentation/dev-tools/gcov.rst is GCC's coverage testing tool, which can be
to get global or per-module coverage. Unlike KCOV, it does not record per-task used with the kernel to get global or per-module coverage. Unlike KCOV, it
coverage. Coverage data can be read from debugfs, and interpreted using the does not record per-task coverage. Coverage data can be read from debugfs,
usual gcov tooling. and interpreted using the usual gcov tooling.
:doc:`kcov` is a feature which can be built in to the kernel to allow Documentation/dev-tools/kcov.rst is a feature which can be built in to the
capturing coverage on a per-task level. It's therefore useful for fuzzing and kernel to allow capturing coverage on a per-task level. It's therefore useful
other situations where information about code executed during, for example, a for fuzzing and other situations where information about code executed during,
single syscall is useful. for example, a single syscall is useful.
Dynamic Analysis Tools Dynamic Analysis Tools