From: patchwork-bot+netdevbpf@kernel.org
To: Florent Revest <revest@chromium.org>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kpsingh@kernel.org, mykolal@fb.com, martin.lau@linux.dev,
song@kernel.org, xukuohai@huaweicloud.com, mark.rutland@arm.com
Subject: Re: [PATCH bpf-next] selftests/bpf: Update the aarch64 tests deny list
Date: Thu, 27 Apr 2023 20:10:19 +0000 [thread overview]
Message-ID: <168262621972.29037.2266972486752352083.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230427143207.635263-1-revest@chromium.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 27 Apr 2023 16:32:07 +0200 you wrote:
> Now that ftrace supports direct call on arm64, BPF tracing programs work
> on that architecture. This fixes the vast majority of BPF selftests
> except for:
>
> - multi_kprobe programs which require fprobe, not available on arm64 yet
> - tracing_struct which requires trampoline support to access struct args
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Update the aarch64 tests deny list
https://git.kernel.org/bpf/bpf-next/c/a46441192084
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:[~2023-04-27 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 14:32 [PATCH bpf-next] selftests/bpf: Update the aarch64 tests deny list Florent Revest
2023-04-27 14:52 ` Florent Revest
2023-04-27 18:56 ` Stanislav Fomichev
2023-04-27 20:10 ` Daniel Borkmann
2023-04-27 20: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=168262621972.29037.2266972486752352083.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=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=revest@chromium.org \
--cc=song@kernel.org \
--cc=xukuohai@huaweicloud.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