From: patchwork-bot+netdevbpf@kernel.org
To: Harishankar Vishwanathan <harishankar.vishwanathan@gmail.com>
Cc: alexei.starovoitov@gmail.com,
harishankar.vishwanathan@rutgers.edu, andrii@kernel.org,
sn624@cs.rutgers.edu, sn349@cs.rutgers.edu,
m.shachnai@rutgers.edu, paul@isovalent.com, daniel@iogearbox.net,
ast@kernel.org, john.fastabend@gmail.com, martin.lau@linux.dev,
eddyz87@gmail.com, song@kernel.org, yonghong.song@linux.dev,
kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
jolsa@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bpf-next: Avoid goto in regs_refine_cond_op()
Date: Thu, 21 Mar 2024 19:00:28 +0000 [thread overview]
Message-ID: <171104762802.29533.11593097586818264707.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240321002955.808604-1-harishankar.vishwanathan@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 20 Mar 2024 20:29:54 -0400 you wrote:
> In case of GE/GT/SGE/JST instructions, regs_refine_cond_op()
> reuses the logic that does analysis of LE/LT/SLE/SLT instructions.
> This commit avoids the use of a goto to perform the reuse.
>
> Signed-off-by: Harishankar Vishwanathan <harishankar.vishwanathan@gmail.com>
> ---
> kernel/bpf/verifier.c | 22 +++++++++++++---------
> 1 file changed, 13 insertions(+), 9 deletions(-)
Here is the summary with links:
- bpf-next: Avoid goto in regs_refine_cond_op()
https://git.kernel.org/bpf/bpf-next/c/4c2a26fc80bc
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:[~2024-03-21 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 0:29 [PATCH] bpf-next: Avoid goto in regs_refine_cond_op() Harishankar Vishwanathan
2024-03-21 19:00 ` 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=171104762802.29533.11593097586818264707.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--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=harishankar.vishwanathan@gmail.com \
--cc=harishankar.vishwanathan@rutgers.edu \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.shachnai@rutgers.edu \
--cc=martin.lau@linux.dev \
--cc=paul@isovalent.com \
--cc=sdf@google.com \
--cc=sn349@cs.rutgers.edu \
--cc=sn624@cs.rutgers.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.