From: patchwork-bot+netdevbpf@kernel.org
To: Luis Gerhorst <luis.gerhorst@fau.de>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, mykolal@fb.com, shuah@kernel.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, hbathini@linux.ibm.com,
christophe.leroy@csgroup.eu, naveen@kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: Support ppc64el in vmtest
Date: Mon, 23 Jun 2025 16:40:06 +0000 [thread overview]
Message-ID: <175069680651.3229526.12855856215912953909.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250619140854.2135283-1-luis.gerhorst@fau.de>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 19 Jun 2025 16:08:53 +0200 you wrote:
> With a rootfs built using libbpf's BPF CI [1], we can run specific tests
> as follows:
>
> $ ../libbpf-ci/rootfs/mkrootfs_debian.sh --arch ppc64el --distro noble
> $ PLATFORM=ppc64el CROSS_COMPILE=powerpc64le-linux-gnu- \
> tools/testing/selftests/bpf/vmtest.sh \
> -l libbpf-vmtest-rootfs-*-noble-ppc64el.tar.zst \
> -- ./test_progs -t verifier_array_access
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Support ppc64el in vmtest
https://git.kernel.org/bpf/bpf-next/c/3ce7cdde66e6
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:[~2025-06-23 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 14:08 Luis Gerhorst
2025-06-23 16:40 ` 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=175069680651.3229526.12855856215912953909.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=christophe.leroy@csgroup.eu \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=hbathini@linux.ibm.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luis.gerhorst@fau.de \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=naveen@kernel.org \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--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
all inboxes | Powered by JetHome®