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, martin.lau@linux.dev, kernel-team@fb.com,
yhs@fb.com
Subject: Re: [PATCH bpf-next 0/2] verifier/xdp_direct_packet_access.c converted to inline assembly
Date: Tue, 28 Mar 2023 21:50:18 +0000 [thread overview]
Message-ID: <168004021823.3305.10312090785832689380.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230328020813.392560-1-eddyz87@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 28 Mar 2023 05:08:11 +0300 you wrote:
> verifier/xdp_direct_packet_access.c automatically converted to inline
> assembly using [1].
>
> This is a leftover from [2], the last patch in a batch was blocked by
> mail server for being too long. This patch-set splits it in two:
> - one to add migrated test to progs/
> - one to remove old test from verifier/
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] selftests/bpf: verifier/xdp_direct_packet_access.c converted to inline assembly
https://git.kernel.org/bpf/bpf-next/c/6e9e141a7a28
- [bpf-next,2/2] selftests/bpf: remove verifier/xdp_direct_packet_access.c, converted to progs/verifier_xdp_direct_packet_access.c
https://git.kernel.org/bpf/bpf-next/c/c63a7d8bbb54
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-03-28 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 2:08 [PATCH bpf-next 0/2] verifier/xdp_direct_packet_access.c converted to inline assembly Eduard Zingerman
2023-03-28 2:08 ` [PATCH bpf-next 1/2] selftests/bpf: " Eduard Zingerman
2023-03-28 2:08 ` [PATCH bpf-next 2/2] selftests/bpf: remove verifier/xdp_direct_packet_access.c, converted to progs/verifier_xdp_direct_packet_access.c Eduard Zingerman
2023-03-28 21: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=168004021823.3305.10312090785832689380.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=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--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