From: Daniel Borkmann <daniel@iogearbox.net>
To: John Fastabend <john.fastabend@gmail.com>, ast@kernel.org
Cc: netdev@vger.kernel.org
Subject: Re: [bpf-next PATCH 0/4] selftests for BPF sockmap use cases
Date: Wed, 25 Apr 2018 00:22:54 +0200 [thread overview]
Message-ID: <04fc2274-837c-6796-1cc7-36eb0b1574ff@iogearbox.net> (raw)
In-Reply-To: <20180423212506.20332.6762.stgit@john-Precision-Tower-5810>
On 04/23/2018 11:30 PM, John Fastabend wrote:
> This series moves ./samples/sockmap into BPF selftests. There are a
> few good reasons to do this. First, by pushing this into selftests
> the tests will be run automatically. Second, sockmap was not really
> a sample of anything anymore, but rather a large set of tests.
>
> Note: There are three recent fixes outstanding against bpf branch
> that can be detected occosionally by the automated tests here.
>
> https://patchwork.ozlabs.org/patch/903138/
> https://patchwork.ozlabs.org/patch/903139/
> https://patchwork.ozlabs.org/patch/903140/
>
> ---
>
> John Fastabend (4):
> bpf: sockmap, code sockmap_test in C
> bpf: sockmap, add a set of tests to run by default
> bpf: sockmap, add selftests
> bpf: sockmap, remove samples program
Applied to bpf-next, thanks John!
prev parent reply other threads:[~2018-04-24 22:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 21:30 [bpf-next PATCH 0/4] selftests for BPF sockmap use cases John Fastabend
2018-04-23 21:30 ` [bpf-next PATCH 1/4] bpf: sockmap, code sockmap_test in C John Fastabend
2018-04-23 21:30 ` [bpf-next PATCH 2/4] bpf: sockmap, add a set of tests to run by default John Fastabend
2018-04-23 21:30 ` [bpf-next PATCH 3/4] bpf: sockmap, add selftests John Fastabend
2018-04-23 21:30 ` [bpf-next PATCH 4/4] bpf: sockmap, remove samples program John Fastabend
2018-04-24 22:22 ` Daniel Borkmann [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=04fc2274-837c-6796-1cc7-36eb0b1574ff@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=john.fastabend@gmail.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