From: Ahmad Wicaksono <supersonix03@gmail.com>
To: bpf@vger.kernel.org
Cc: rhkrqnwk98@gmail.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, john.fastabend@gmail.com, corbet@lwn.net,
linux-doc@vger.kernel.org,
Ahmad Wicaksono <supersonix03@gmail.com>
Subject: [PATCH bpf-next 2/2] Documentation/bpf: Fix stale selftests file references
Date: Sun, 15 Nov 2026 00:01:17 +0700 [thread overview]
Message-ID: <20261114170117.196552-3-supersonix03@gmail.com> (raw)
In-Reply-To: <20261114170117.196552-1-supersonix03@gmail.com>
Two selftests paths in the BPF docs no longer exist:
map_lpm_trie.rst points at tools/testing/selftests/bpf/test_lpm_map.c,
which was moved by commit 3e18f5f1e5a1 ("selftests/bpf: Move
test_lpm_map.c to map_tests") and now lives at
tools/testing/selftests/bpf/map_tests/lpm_trie_map_basic_ops.c.
btf.rst points at tools/testing/selftests/bpf/test_xdp_noinline.c, which
is now tools/testing/selftests/bpf/progs/test_xdp_noinline.c.
Update both so readers can find the code.
Signed-off-by: Ahmad Wicaksono <supersonix03@gmail.com>
---
Documentation/bpf/btf.rst | 2 +-
Documentation/bpf/map_lpm_trie.rst | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/bpf/btf.rst b/Documentation/bpf/btf.rst
index b618812390e..94a81a9e99b 100644
--- a/Documentation/bpf/btf.rst
+++ b/Documentation/bpf/btf.rst
@@ -1148,7 +1148,7 @@ information.::
The following is an example of how line_info can help debugging verification
failure.::
- /* The code at tools/testing/selftests/bpf/test_xdp_noinline.c
+ /* The code at tools/testing/selftests/bpf/progs/test_xdp_noinline.c
* is modified as below.
*/
data = (void *)(long)xdp->data;
diff --git a/Documentation/bpf/map_lpm_trie.rst b/Documentation/bpf/map_lpm_trie.rst
index f9cd579496c..37ef39d0b39 100644
--- a/Documentation/bpf/map_lpm_trie.rst
+++ b/Documentation/bpf/map_lpm_trie.rst
@@ -108,9 +108,9 @@ specific keys before less specific ones.
Examples
========
-Please see ``tools/testing/selftests/bpf/test_lpm_map.c`` for examples
-of LPM trie usage from userspace. The code snippets below demonstrate
-API usage.
+Please see ``tools/testing/selftests/bpf/map_tests/lpm_trie_map_basic_ops.c``
+for examples of LPM trie usage from userspace. The code snippets below
+demonstrate API usage.
Kernel BPF
----------
--
2.43.0
next prev parent reply other threads:[~2026-11-14 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 17:01 [PATCH bpf-next 0/2] Documentation/bpf: Fix stale references in map docs Ahmad Wicaksono
2026-11-14 17:01 ` [PATCH bpf-next 1/2] Documentation/bpf: Update sockmap docs for mutation restrictions Ahmad Wicaksono
2026-11-16 18:51 ` Jakub Sitnicki
2026-11-17 5:10 ` Alexei Starovoitov
2026-11-14 17:01 ` Ahmad Wicaksono [this message]
2026-11-16 18:52 ` [PATCH bpf-next 2/2] Documentation/bpf: Fix stale selftests file references Jakub Sitnicki
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=20261114170117.196552-3-supersonix03@gmail.com \
--to=supersonix03@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=rhkrqnwk98@gmail.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.