From: Daniel Borkmann <daniel@iogearbox.net>
To: John Fastabend <john.fastabend@gmail.com>, netdev@vger.kernel.org
Cc: john.r.fastabend@intel.com, jakub.kicinski@netronome.com
Subject: Re: [PATCH] bpf: testing: fix devmap tests
Date: Thu, 27 Jul 2017 02:40:28 +0200 [thread overview]
Message-ID: <5979367C.4020408@iogearbox.net> (raw)
In-Reply-To: <20170727003206.16649.50637.stgit@john-Precision-Tower-5810>
On 07/27/2017 02:32 AM, John Fastabend wrote:
> Apparently through one of my revisions of the initial patches
> series I lost the devmap test. We can add more testing later but
> for now lets fix the simple one we have.
>
> Fixes: 546ac1ffb70d "bpf: add devmap, a map for storing net device references"
> Reported-by: Jakub Kicinski <jakub.kicinski@netronome.com>
> Signed-off-by: John Fastabend <john.fastabend@gmail.com>
Looks good, thanks!
Acked-by: Daniel Borkmann <daniel@iogearbox.net>
prev parent reply other threads:[~2017-07-27 0:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 0:32 [PATCH] bpf: testing: fix devmap tests John Fastabend
2017-07-27 0:35 ` John Fastabend
2017-07-29 21:13 ` David Miller
2017-07-27 0:40 ` 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=5979367C.4020408@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=jakub.kicinski@netronome.com \
--cc=john.fastabend@gmail.com \
--cc=john.r.fastabend@intel.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).