From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, yhs@fb.com,
john.fastabend@gmail.com, shung-hsi.yu@suse.com
Subject: Re: [PATCH bpf-next v3 0/2] propagate nullness information for reg to reg comparisons
Date: Wed, 16 Nov 2022 01:50:16 +0000 [thread overview]
Message-ID: <166856341600.14321.8341346662749617432.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221115224859.2452988-1-eddyz87@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 16 Nov 2022 00:48:57 +0200 you wrote:
> This patchset adds ability to propagates nullness information for
> branches of register to register equality compare instructions. The
> following rules are used:
> - suppose register A maybe null
> - suppose register B is not null
> - for JNE A, B, ... - A is not null in the false branch
> - for JEQ A, B, ... - A is not null in the true branch
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/2] bpf: propagate nullness information for reg to reg comparisons
https://git.kernel.org/bpf/bpf-next/c/befae75856ab
- [bpf-next,v3,2/2] selftests/bpf: check nullness propagation for reg to reg comparisons
https://git.kernel.org/bpf/bpf-next/c/4741c371aa08
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:[~2022-11-16 1:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 22:48 [PATCH bpf-next v3 0/2] propagate nullness information for reg to reg comparisons Eduard Zingerman
2022-11-15 22:48 ` [PATCH bpf-next v3 1/2] bpf: " Eduard Zingerman
2022-11-15 22:48 ` [PATCH bpf-next v3 2/2] selftests/bpf: check nullness propagation " Eduard Zingerman
2022-11-16 1:50 ` 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=166856341600.14321.8341346662749617432.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=john.fastabend@gmail.com \
--cc=kernel-team@fb.com \
--cc=shung-hsi.yu@suse.com \
--cc=yhs@fb.com \
/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