From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
kafai@fb.com, john.fastabend@gmail.com, kernel-team@fb.com,
netdev@vger.kernel.org, edumazet@google.com, brakmo@fb.com,
andrii.nakryiko@gmail.com, alexanderduyck@fb.com
Subject: Re: [bpf-next PATCH v3 1/5] selftests/bpf: Move test_tcppbf_user into test_progs
Date: Wed, 04 Nov 2020 02:10:04 +0000 [thread overview]
Message-ID: <160445580494.31301.3509278420487105425.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <160443928881.1086697.17661359319919165370.stgit@localhost.localdomain>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Tue, 03 Nov 2020 13:34:48 -0800 you wrote:
> From: Alexander Duyck <alexanderduyck@fb.com>
>
> Recently a bug was missed due to the fact that test_tcpbpf_user is not a
> part of test_progs. In order to prevent similar issues in the future move
> the test functionality into test_progs. By doing this we can make certain
> that it is a part of standard testing and will not be overlooked.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/5] selftests/bpf: Move test_tcppbf_user into test_progs
https://git.kernel.org/bpf/bpf-next/c/aaf376bddf68
- [bpf-next,v3,2/5] selftests/bpf: Drop python client/server in favor of threads
https://git.kernel.org/bpf/bpf-next/c/247f0ec361b7
- [bpf-next,v3,3/5] selftests/bpf: Replace EXPECT_EQ with ASSERT_EQ and refactor verify_results
https://git.kernel.org/bpf/bpf-next/c/d3813ea14b69
- [bpf-next,v3,4/5] selftests/bpf: Migrate tcpbpf_user.c to use BPF skeleton
https://git.kernel.org/bpf/bpf-next/c/0a099d1429c7
- [bpf-next,v3,5/5] selftest/bpf: Use global variables instead of maps for test_tcpbpf_kern
https://git.kernel.org/bpf/bpf-next/c/21b5177e997c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2020-11-04 2:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 21:34 [bpf-next PATCH v3 0/5] selftests/bpf: Migrate test_tcpbpf_user to be a part of test_progs framework Alexander Duyck
2020-11-03 21:34 ` [bpf-next PATCH v3 1/5] selftests/bpf: Move test_tcppbf_user into test_progs Alexander Duyck
2020-11-04 2:10 ` patchwork-bot+netdevbpf [this message]
2020-11-03 21:34 ` [bpf-next PATCH v3 2/5] selftests/bpf: Drop python client/server in favor of threads Alexander Duyck
2020-11-03 21:35 ` [bpf-next PATCH v3 3/5] selftests/bpf: Replace EXPECT_EQ with ASSERT_EQ and refactor verify_results Alexander Duyck
2020-11-03 21:35 ` [bpf-next PATCH v3 4/5] selftests/bpf: Migrate tcpbpf_user.c to use BPF skeleton Alexander Duyck
2020-11-03 21:35 ` [bpf-next PATCH v3 5/5] selftest/bpf: Use global variables instead of maps for test_tcpbpf_kern Alexander Duyck
2020-11-04 0:20 ` [bpf-next PATCH v3 0/5] selftests/bpf: Migrate test_tcpbpf_user to be a part of test_progs framework Martin KaFai Lau
2020-11-04 2:01 ` Alexei Starovoitov
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=160445580494.31301.3509278420487105425.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexander.duyck@gmail.com \
--cc=alexanderduyck@fb.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brakmo@fb.com \
--cc=daniel@iogearbox.net \
--cc=edumazet@google.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kernel-team@fb.com \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).