From: patchwork-bot+netdevbpf@kernel.org
To: Jie Meng <jmeng@fb.com>
Cc: alexei.starovoitov@gmail.com, andrii@kernel.org, ast@kernel.org,
bpf@vger.kernel.org, daniel@iogearbox.net
Subject: Re: [PATCH bpf-next v3] bpf/tests: Exhaustive test coverage for signed division and modulo
Date: Tue, 21 Apr 2026 01:00:17 +0000 [thread overview]
Message-ID: <177673321782.2153798.645802776680102725.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260413172311.3918767-1-jmeng@fb.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 13 Apr 2026 10:23:11 -0700 you wrote:
> Extend lib/test_bpf.c to provide comprehensive test coverage for BPF
> signed division (SDIV) and signed modulo (SMOD) instructions, both
> 32-bit and 64-bit variants with immediate operands.
>
> Introduce F_ALU32 and F_SIGNED flags to replace the less readable
> bool alu32 and s16 off parameters throughout the test helpers. The
> BPF instruction 'off' field is derived from flags only at the point
> of instruction encoding.
>
> [...]
Here is the summary with links:
- [bpf-next,v3] bpf/tests: Exhaustive test coverage for signed division and modulo
https://git.kernel.org/bpf/bpf-next/c/c8f0ee969f76
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-04-21 1:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 20:50 [PATCH bpf-next] bpf/tests: Exhaustive test coverage for signed division and modulo Jie Meng
2026-04-02 22:16 ` Alexei Starovoitov
2026-04-06 20:39 ` [PATCH v2] " Jie Meng
2026-04-11 17:40 ` Alexei Starovoitov
2026-04-13 17:23 ` [PATCH bpf-next v3] " Jie Meng
2026-04-21 1: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=177673321782.2153798.645802776680102725.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=jmeng@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