From: patchwork-bot+netdevbpf@kernel.org
To: Kexin Sun <kexinsun@smail.nju.edu.cn>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org,
sdf@fomichev.me, haoluo@google.com, jolsa@kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
julia.lawall@inria.fr, xutong.ma@inria.fr, yunbolyu@smu.edu.sg,
ratnadiraw@smu.edu.sg
Subject: Re: [PATCH] bpf: update outdated comment for refactored btf_check_kfunc_arg_match()
Date: Tue, 24 Mar 2026 20:40:17 +0000 [thread overview]
Message-ID: <177438481754.1297770.5595980549386227407.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260321105658.6006-1-kexinsun@smail.nju.edu.cn>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 21 Mar 2026 18:56:58 +0800 you wrote:
> The function btf_check_kfunc_arg_match() was refactored into
> check_kfunc_args() by commit 00b85860feb8 ("bpf: Rewrite kfunc
> argument handling"). Update the comment accordingly.
>
> Assisted-by: unnamed:deepseek-v3.2 coccinelle
> Signed-off-by: Kexin Sun <kexinsun@smail.nju.edu.cn>
>
> [...]
Here is the summary with links:
- bpf: update outdated comment for refactored btf_check_kfunc_arg_match()
https://git.kernel.org/bpf/bpf-next/c/70b5f3f7822a
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-03-24 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 10:56 [PATCH] bpf: update outdated comment for refactored btf_check_kfunc_arg_match() Kexin Sun
2026-03-21 15:20 ` Yonghong Song
2026-03-23 7:39 ` Jiayuan Chen
2026-03-24 20: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=177438481754.1297770.5595980549386227407.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=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=julia.lawall@inria.fr \
--cc=kexinsun@smail.nju.edu.cn \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=ratnadiraw@smu.edu.sg \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=xutong.ma@inria.fr \
--cc=yonghong.song@linux.dev \
--cc=yunbolyu@smu.edu.sg \
/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