From: patchwork-bot+netdevbpf@kernel.org
To: Nirbhay Sharma <nirbhay.lkd@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, skhan@linuxfoundation.org,
david.hunter.linux@gmail.com,
linux-kernel-mentees@lists.linuxfoundation.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] bpf: Document cfi_stubs and owner fields in struct bpf_struct_ops
Date: Thu, 20 Nov 2025 22:10:09 +0000 [thread overview]
Message-ID: <176367660986.1804570.2226125940401582306.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251120204620.59571-2-nirbhay.lkd@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Fri, 21 Nov 2025 02:16:21 +0530 you wrote:
> Add missing kernel-doc documentation for the cfi_stubs and owner
> fields in struct bpf_struct_ops to fix the following warnings:
>
> Warning: include/linux/bpf.h:1931 struct member 'cfi_stubs' not
> described in 'bpf_struct_ops'
> Warning: include/linux/bpf.h:1931 struct member 'owner' not
> described in 'bpf_struct_ops'
>
> [...]
Here is the summary with links:
- [v2] bpf: Document cfi_stubs and owner fields in struct bpf_struct_ops
https://git.kernel.org/bpf/bpf-next/c/e0940c672ab4
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:[~2025-11-20 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 6:24 [PATCH] bpf: Document cfi_stubs and owner fields in struct bpf_struct_ops Nirbhay Sharma
2025-11-20 19:29 ` Martin KaFai Lau
2025-11-20 20:46 ` [PATCH v2] " Nirbhay Sharma
2025-11-20 22:10 ` 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=176367660986.1804570.2226125940401582306.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=daniel@iogearbox.net \
--cc=david.hunter.linux@gmail.com \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=nirbhay.lkd@gmail.com \
--cc=sdf@fomichev.me \
--cc=skhan@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox