From: patchwork-bot+netdevbpf@kernel.org
To: Karl Mehltretter <kmehltretter@gmail.com>
Cc: 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,
bpf@vger.kernel.org, corbet@lwn.net, linux-doc@vger.kernel.org,
skhan@linuxfoundation.org, rdunlap@infradead.org,
void@manifault.com
Subject: Re: [PATCH bpf-next v2] bpf, docs: Fix two struct names in btf.rst and kfuncs.rst
Date: Fri, 11 Sep 2026 17:40:05 +0000 [thread overview]
Message-ID: <178914840504.3026440.16596619579892095283.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260906222656.3459-1-kmehltretter@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 7 Sep 2026 00:26:56 +0200 you wrote:
> 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>
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpf, docs: Fix two struct names in btf.rst and kfuncs.rst
https://git.kernel.org/bpf/bpf-next/c/cf95f22a06b2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-11 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 22:26 [PATCH bpf-next v2] bpf, docs: Fix two struct names in btf.rst and kfuncs.rst Karl Mehltretter
2026-09-11 17:40 ` patchwork-bot+netdevbpf [this message]
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=178914840504.3026440.16596619579892095283.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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=kmehltretter@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox