From: patchwork-bot+netdevbpf@kernel.org
To: Shung-Hsi Yu <shung-hsi.yu@suse.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
john.fastabend@gmail.com, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
jolsa@kernel.org, eddyz87@gmail.com
Subject: Re: [PATCH bpf-next] bpf: replace register_is_const() with is_reg_const()
Date: Thu, 09 Nov 2023 18:30:24 +0000 [thread overview]
Message-ID: <169955462477.11926.14918758803007867967.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231108140043.12282-1-shung-hsi.yu@suse.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 8 Nov 2023 22:00:41 +0800 you wrote:
> The addition of is_reg_const() in commit 171de12646d2 ("bpf: generalize
> is_branch_taken to handle all conditional jumps in one place") has made the
> register_is_const() redundent. Give the former has more feature, plus the
> fact the latter is only used in one place, replace register_is_const() with
> is_reg_const(), and remove the definition of register_is_const.
>
> This requires moving the definition of is_reg_const() further up. And since
> the comment of reg_const_value() reference is_reg_const(), move it up as
> well.
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: replace register_is_const() with is_reg_const()
https://git.kernel.org/bpf/bpf-next/c/3815f89592d5
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:[~2023-11-09 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 14:00 [PATCH bpf-next] bpf: replace register_is_const() with is_reg_const() Shung-Hsi Yu
2023-11-08 22:46 ` Andrii Nakryiko
2023-11-09 18:30 ` 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=169955462477.11926.14918758803007867967.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=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=shung-hsi.yu@suse.com \
--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