@@ -441,8 +441,7 @@ compatible board:1.**ARM 64 Tool Chain**- For example, the *aarch64* Linaro Toolchain, which can be obtained from-`here <https://releases.linaro.org/components/toolchain/binaries/4.9-2017.01/aarch64-linux-gnu>`_.+ For example, the `*aarch64* Linaro Toolchain <https://releases.linaro.org/components/toolchain/binaries/4.9-2017.01/aarch64-linux-gnu>`_.2.**Linux Kernel**
@@ -441,8 +441,7 @@ compatible board:1.**ARM 64 Tool Chain**- For example, the *aarch64* Linaro Toolchain, which can be obtained from-`here <https://releases.linaro.org/components/toolchain/binaries/4.9-2017.01/aarch64-linux-gnu>`_.+ For example, the `*aarch64* Linaro Toolchain <https://releases.linaro.org/components/toolchain/binaries/4.9-2017.01/aarch64-linux-gnu>`_.2.**Linux Kernel**
@@ -441,8 +441,7 @@ compatible board:1.**ARM 64 Tool Chain**- For example, the *aarch64* Linaro Toolchain, which can be obtained from-`here <https://releases.linaro.org/components/toolchain/binaries/4.9-2017.01/aarch64-linux-gnu>`_.+ For example, the `*aarch64* Linaro Toolchain <https://releases.linaro.org/components/toolchain/binaries/4.9-2017.01/aarch64-linux-gnu>`_.2.**Linux Kernel**
I am not sure how to specific in patch that it applies on dpdk-net-next
in response to [1].
I don't know either :), but thanks for letting know, I will check it.
What is the build warning?
Also, the existing version with the `here <link>`_ format is better since
it doesn't put a long url into the text. Probably it is better to fix that
if it that is the issue.
What is the build warning?
Also, the existing version with the `here <link>`_ format is better since
it doesn't put a long url into the text. Probably it is better to fix that
if it that is the issue.
Whoops, sorry. I misread the patch. I see that you are still using `here <link>`_
so disregard that comment.
I would still be good to see the build issue though.
What is the build warning?
Also, the existing version with the `here <link>`_ format is better since
it doesn't put a long url into the text. Probably it is better to fix that
if it that is the issue.
The doc has two 'here ...' text references. As soon as I remove one of
them, the warning (WARNING: Duplicate explicit target name: "here") is
generated.
I am not sure of the reason so I resorted to replacing one of the
'here..' links.
What is the build warning?
Also, the existing version with the `here <link>`_ format is better since
it doesn't put a long url into the text. Probably it is better to fix that
if it that is the issue.
Whoops, sorry. I misread the patch. I see that you are still using `here <link>`_
so disregard that comment.
I think there is some confusion. I have removed the string "here" and
replaced that with another running text having the original link.
I would still be good to see the build issue though.
The warning being shown on non-patched dpaa2.rst is:
--->8---
sphinx processing guides-html...
/home/shreyansh/build/DPDK/06_dpdk/doc/guides/nics/dpaa2.rst:32:
WARNING: Duplicate explicit target name: "here".
--->8--
-
Shreyansh
@@ -441,8 +441,7 @@ compatible board:1.**ARM 64 Tool Chain**- For example, the *aarch64* Linaro Toolchain, which can be obtained from-`here <https://releases.linaro.org/components/toolchain/binaries/4.9-2017.01/aarch64-linux-gnu>`_.+ For example, the `*aarch64* Linaro Toolchain <https://releases.linaro.org/components/toolchain/binaries/4.9-2017.01/aarch64-linux-gnu>`_.2.**Linux Kernel**
I am not sure how to specific in patch that it applies on dpdk-net-next
in response to [1].
I don't know either :), but thanks for letting know, I will check it.
I confirm this fixes the documentation warning, patch squashed into
relevant commit (17a4c3c16f5c)