From: patchwork-bot+netdevbpf@kernel.org
To: Tiezhu Yang <yangtiezhu@loongson.cn>
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,
emil@etsalapatis.com, kafai.wan@linux.dev, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v1] bpf: Use BPF_CALL_IMM macro consistently in bpf_do_misc_fixups
Date: Wed, 01 Jul 2026 20:10:06 +0000 [thread overview]
Message-ID: <178293660664.1278318.10938621476136606874.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260701035107.8069-1-yangtiezhu@loongson.cn>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 1 Jul 2026 11:51:07 +0800 you wrote:
> In bpf_do_misc_fixups(), the conversion from a function address to a
> BPF immediate value is handled using the BPF_CALL_IMM macro inside the
> 'patch_map_ops_generic' label block. However, immediately following it
> in the 'patch_call_imm' label block, the immediate value is calculated
> manually by subtracting __bpf_call_base from fn->func.
>
> Inspired by KaFai Wan's review comments on fixing helper call offsets,
> use the BPF_CALL_IMM macro in 'patch_call_imm' as well to clean this up.
> This removes the redundant manual pointer arithmetic and ensures coding
> style consistency across adjacent label blocks within the same function.
>
> [...]
Here is the summary with links:
- [bpf-next,v1] bpf: Use BPF_CALL_IMM macro consistently in bpf_do_misc_fixups
https://git.kernel.org/bpf/bpf-next/c/475b59db3bd5
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-07-01 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 3:51 [PATCH bpf-next v1] bpf: Use BPF_CALL_IMM macro consistently in bpf_do_misc_fixups Tiezhu Yang
2026-07-01 20: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=178293660664.1278318.10938621476136606874.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=emil@etsalapatis.com \
--cc=jolsa@kernel.org \
--cc=kafai.wan@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=song@kernel.org \
--cc=yangtiezhu@loongson.cn \
--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