From: patchwork-bot+netdevbpf@kernel.org
To: Delyan Kratunov <delyank@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net
Subject: Re: [PATCH bpf-next v3 0/4] migrate from bpf_prog_test_run{,_xattr}
Date: Thu, 03 Feb 2022 07:20:09 +0000 [thread overview]
Message-ID: <164387280940.12689.14794056106613700107.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220202235423.1097270-1-delyank@fb.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 2 Feb 2022 15:54:19 -0800 you wrote:
> Fairly straight-forward mechanical transformation from bpf_prog_test_run
> and bpf_prog_test_run_xattr to the bpf_prog_test_run_opts goodness.
>
> I did a fair amount of drive-by CHECK/CHECK_ATTR cleanups as well, though
> certainly not everything possible. Primarily, I did not want to just change
> arguments to CHECK calls, though I had to do a bit more than that
> in some cases (overall, -119 CHECK calls and all CHECK_ATTR calls).
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/4] selftests/bpf: migrate from bpf_prog_test_run
https://git.kernel.org/bpf/bpf-next/c/04fcb5f9a104
- [bpf-next,v3,2/4] selftests/bpf: migrate from bpf_prog_test_run_xattr
https://git.kernel.org/bpf/bpf-next/c/393161837845
- [bpf-next,v3,3/4] bpftool: migrate from bpf_prog_test_run_xattr
https://git.kernel.org/bpf/bpf-next/c/9cce53138dd9
- [bpf-next,v3,4/4] libbpf: Deprecate bpf_prog_test_run_xattr and bpf_prog_test_run
https://git.kernel.org/bpf/bpf-next/c/3e1ab843d2d4
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:[~2022-02-03 7:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 23:54 [PATCH bpf-next v3 0/4] migrate from bpf_prog_test_run{,_xattr} Delyan Kratunov
2022-02-02 23:54 ` [PATCH bpf-next v3 1/4] selftests/bpf: migrate from bpf_prog_test_run Delyan Kratunov
2022-02-02 23:54 ` [PATCH bpf-next v3 2/4] selftests/bpf: migrate from bpf_prog_test_run_xattr Delyan Kratunov
2022-02-02 23:54 ` [PATCH bpf-next v3 3/4] bpftool: " Delyan Kratunov
2022-02-02 23:54 ` [PATCH bpf-next v3 4/4] libbpf: Deprecate bpf_prog_test_run_xattr and bpf_prog_test_run Delyan Kratunov
2022-02-03 7:11 ` [PATCH bpf-next v3 0/4] migrate from bpf_prog_test_run{,_xattr} Andrii Nakryiko
2022-02-03 7:20 ` 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=164387280940.12689.14794056106613700107.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=delyank@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