docs: repair broken references
cover docs: repair broken references
Found while doing other work for the QAPI generator.
John Snow (1):
docs: repair broken references
docs/devel/multi-thread-tcg.rst | 2 +- docs/devel/testing.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
Signature · 1 line
2.26.2
PATCH 1/1 docs: repair broken references
In two different places, we are making a cross-reference to some resource incorrectly. These were being interpreted as "content" instead of a link and a reference, accordingly.
Signed-off-by John Snow <[email protected]>
--- docs/devel/multi-thread-tcg.rst | 2 +- docs/devel/testing.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
docs/devel/multi-thread-tcg.rst +1 -1
@@ -267,7 +267,7 @@ of view of external observers (e.g. another processor core). They can apply to any memory operations as well as just loads or stores. The Linux kernel has an excellent `write-up -<https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/Documentation/memory-barriers.txt>` +<https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/Documentation/memory-barriers.txt>`_ on the various forms of memory barrier and the guarantees they can provide.
docs/devel/testing.rst +1 -1
@@ -953,7 +953,7 @@ compiler flags are needed to build for a given target. If you have the ability to run containers as the user you can also take advantage of the build systems "Docker" support. It will then use containers to build any test case for an enabled guest where there is -no system compiler available. See :ref: `_docker-ref` for details. +no system compiler available. See :ref:`docker-ref` for details. Running subset of tests -----------------------
Signature · 1 line
2.26.2