From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux BPF <bpf@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Jesper Dangaard Brouer <brouer@redhat.com>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH 0/2] Hyperlink fixes for BPF QA documentation
Date: Tue, 28 Feb 2023 14:45:21 +0700 [thread overview]
Message-ID: <20230228074523.11493-1-bagasdotme@gmail.com> (raw)
When the broken link fix for Documentation/bpf/bpf_devel_QA.rst was
applied, Daniel Borkmann asked me to also fix some other links in the
documentation [1]. So here is the series.
The fixes in the shortlog below should be self-explanatory.
[1]: https://lore.kernel.org/linux-doc/7cd545a2-4a5c-1961-1cf7-cd0f24e41df8@iogearbox.net/
Bagas Sanjaya (2):
Documentation: bpf: Do not link to docs.kernel.org for kselftest link
Documentation: bpf: Link to submitting-patches.rst for general patch
submission info
Documentation/bpf/bpf_devel_QA.rst | 11 ++++-------
1 file changed, 4 insertions(+), 7 deletions(-)
base-commit: 2d311f480b52eeb2e1fd432d64b78d82952c3808
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2023-02-28 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 7:45 Bagas Sanjaya [this message]
2023-02-28 7:45 ` [PATCH 1/2] Documentation: bpf: Do not link to docs.kernel.org for kselftest link Bagas Sanjaya
2023-02-28 7:45 ` [PATCH 2/2] Documentation: bpf: Link to submitting-patches.rst for general patch submission info Bagas Sanjaya
2023-03-06 22:33 ` [PATCH 0/2] Hyperlink fixes for BPF QA documentation Daniel Borkmann
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=20230228074523.11493-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.com \
/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