From: Karl Mehltretter <kmehltretter@gmail.com>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>
Cc: Karl Mehltretter <kmehltretter@gmail.com>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Jiri Olsa <jolsa@kernel.org>,
bpf@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
David Vernet <void@manifault.com>
Subject: [PATCH bpf-next v2] bpf, docs: Fix two struct names in btf.rst and kfuncs.rst
Date: Mon, 7 Sep 2026 00:26:56 +0200 [thread overview]
Message-ID: <20260906222656.3459-1-kmehltretter@gmail.com> (raw)
struct btf_variable and struct bpf_cpmuask do not exist; the names are
struct btf_var and struct bpf_cpumask.
Use them.
Fixes: f063c889c945 ("bpf: add specification for BTF Var and DataSec kinds")
Fixes: 027bdec89364 ("bpf/docs: Document the nocast aliasing behavior of ___init")
Assisted-by: LLM
Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
---
v2: the two one-line fixes combined into one patch, as Alexei asked;
the two Fixes: tags stay because the typos have different origins
Randy's Reviewed-by, given on both v1 postings, collected
v1: https://lore.kernel.org/r/20260905095649.42351-1-kmehltretter@gmail.com/
https://lore.kernel.org/r/20260905095527.42261-1-kmehltretter@gmail.com/
Documentation/bpf/btf.rst | 2 +-
Documentation/bpf/kfuncs.rst | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/bpf/btf.rst b/Documentation/bpf/btf.rst
index 3f05f17990ad..004aa1058d85 100644
--- a/Documentation/bpf/btf.rst
+++ b/Documentation/bpf/btf.rst
@@ -416,7 +416,7 @@ If the function has variable arguments, the last parameter is encoded with
* ``info.vlen``: 0
* ``type``: the type of the variable
-``btf_type`` is followed by a single ``struct btf_variable`` with the
+``btf_type`` is followed by a single ``struct btf_var`` with the
following data::
struct btf_var {
diff --git a/Documentation/bpf/kfuncs.rst b/Documentation/bpf/kfuncs.rst
index 85f73e0bbd0f..57831eda0a33 100644
--- a/Documentation/bpf/kfuncs.rst
+++ b/Documentation/bpf/kfuncs.rst
@@ -536,7 +536,7 @@ For example, for the following type definition:
The verifier would allow a ``struct bpf_cpumask *`` to be passed to a kfunc
taking a ``cpumask_t *`` (which is a typedef of ``struct cpumask *``). For
-instance, both ``struct cpumask *`` and ``struct bpf_cpmuask *`` can be passed
+instance, both ``struct cpumask *`` and ``struct bpf_cpumask *`` can be passed
to bpf_cpumask_test_cpu().
In some cases, this type-aliasing behavior is not desired. ``struct
base-commit: 986c24e0fe44f844b44d365b71ce831947f50298
--
2.53.0
next reply other threads:[~2026-09-06 22:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 22:26 Karl Mehltretter [this message]
2026-09-11 17:40 ` [PATCH bpf-next v2] bpf, docs: Fix two struct names in btf.rst and kfuncs.rst patchwork-bot+netdevbpf
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=20260906222656.3459-1-kmehltretter@gmail.com \
--to=kmehltretter@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=jolsa@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=song@kernel.org \
--cc=void@manifault.com \
--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.