From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: bpf@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/bpf: Fix invalid link of "Documentation/bpf/btf.rst"
Date: Wed, 22 Feb 2023 15:54:11 +0700 [thread overview]
Message-ID: <Y/XYM4D1SW/zyhNJ@debian.me> (raw)
In-Reply-To: <1677035401-3628-1-git-send-email-yangtiezhu@loongson.cn>
[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]
On Wed, Feb 22, 2023 at 11:10:01AM +0800, Tiezhu Yang wrote:
> "Documentation/bpf/btf.rst" is linked to the following invalid web page:
>
> https://www.kernel.org/doc/html/latest/bpf/btf.rst
>
> The correct link should be:
>
> https://www.kernel.org/doc/html/latest/bpf/btf.html
>
> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
Hi,
I have already submitted a different fix to the same problem at [1] (v2
at [2]). Please take a look at there.
[1]: https://lore.kernel.org/linux-doc/20230219030956.22662-1-bagasdotme@gmail.com/
[2]: https://lore.kernel.org/linux-doc/20230222083530.26136-1-bagasdotme@gmail.com/
> diff --git a/Documentation/bpf/bpf_devel_QA.rst b/Documentation/bpf/bpf_devel_QA.rst
> index 03d4993..f54c328 100644
> --- a/Documentation/bpf/bpf_devel_QA.rst
> +++ b/Documentation/bpf/bpf_devel_QA.rst
> @@ -690,6 +690,7 @@ when:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/testing/selftests/bpf/
> .. _Documentation/dev-tools/kselftest.rst:
> https://www.kernel.org/doc/html/latest/dev-tools/kselftest.html
> -.. _Documentation/bpf/btf.rst: btf.rst
> +.. _Documentation/bpf/btf.rst:
> + https://www.kernel.org/doc/html/latest/bpf/btf.html
>
> Happy BPF hacking!
For consistency with my fix above, can you please convert these in-tree links
from using external link to simply write the doc path instead?
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-02-22 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 3:10 [PATCH] docs/bpf: Fix invalid link of "Documentation/bpf/btf.rst" Tiezhu Yang
2023-02-22 8:54 ` Bagas Sanjaya [this message]
2023-02-22 10:06 ` Tiezhu Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y/XYM4D1SW/zyhNJ@debian.me \
--to=bagasdotme@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yangtiezhu@loongson.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).