From: patchwork-bot+netdevbpf@kernel.org
To: adubey <adubey@linux.ibm.com>
Cc: bpf@vger.kernel.org, puranjay@kernel.org, ast@kernel.org,
andrii@kernel.org, daniel@iogearbox.net, martin.lau@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, mykyta.yatsenko5@gmail.com
Subject: Re: [PATCH] selftest/bpf: enable test for instruction array on arm64
Date: Tue, 24 Feb 2026 02:10:06 +0000 [thread overview]
Message-ID: <177189900655.3277452.13026471633191925203.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260223203511.118475-1-adubey@linux.ibm.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 23 Feb 2026 15:35:11 -0500 you wrote:
> From: Abhishek Dubey <adubey@linux.ibm.com>
>
> As arm64 JIT now supports instruction array, make sure
> all relevant tests run on this architecture.
>
> #21/1 bpf_insn_array/one2one:OK
> #21/2 bpf_insn_array/simple:OK
> #21/3 bpf_insn_array/deletions:OK
> #21/4 bpf_insn_array/deletions-with-functions:OK
> #21/5 bpf_insn_array/blindness:OK
> #21/6 bpf_insn_array/incorrect-index:OK
> #21/7 bpf_insn_array/load-unfrozen-map:OK
> #21/8 bpf_insn_array/no-map-reuse:OK
> #21/9 bpf_insn_array/bpf-side-ops:OK
> #21 bpf_insn_array:OK
> Summary: 1/9 PASSED, 0 SKIPPED, 0 FAILED
>
> [...]
Here is the summary with links:
- selftest/bpf: enable test for instruction array on arm64
https://git.kernel.org/bpf/bpf-next/c/99726ece0c8a
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-02-24 2:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 20:35 [PATCH] selftest/bpf: enable test for instruction array on arm64 adubey
2026-02-23 16:17 ` Anton Protopopov
2026-02-24 2: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=177189900655.3277452.13026471633191925203.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=adubey@linux.ibm.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=mykyta.yatsenko5@gmail.com \
--cc=puranjay@kernel.org \
/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