From: John Fastabend <john.fastabend@gmail.com>
To: alexei.starovoitov@gmail.com, daniel@iogearbox.net
Cc: netdev@vger.kernel.org
Subject: [bpf-next PATCH 0/2] bpf: test_sockmap updates
Date: Tue, 28 Aug 2018 09:10:39 -0700 [thread overview]
Message-ID: <20180828160921.24004.71893.stgit@john-Precision-Tower-5810> (raw)
Two small test sockmap updates for bpf-next. These help me run some
additional tests with test_sockmap.
---
John Fastabend (2):
bpf: sockmap test remove shutdown() calls
bpf: use --cgroup in test_suite if supplied
tools/testing/selftests/bpf/test_sockmap.c | 56 ++++++++++++++++------------
1 file changed, 31 insertions(+), 25 deletions(-)
next reply other threads:[~2018-08-28 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 16:10 John Fastabend [this message]
2018-08-28 16:10 ` [bpf-next PATCH 1/2] bpf: sockmap test remove shutdown() calls John Fastabend
2018-08-28 16:10 ` [bpf-next PATCH 2/2] bpf: use --cgroup in test_suite if supplied John Fastabend
2018-08-29 15:38 ` [bpf-next PATCH 0/2] bpf: test_sockmap updates Daniel Borkmann
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=20180828160921.24004.71893.stgit@john-Precision-Tower-5810 \
--to=john.fastabend@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--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