From: Daniel Borkmann <daniel@iogearbox.net>
To: Alexei Starovoitov <ast@fb.com>,
"David S . Miller" <davem@davemloft.net>
Cc: Chenbo Feng <fengc@google.com>,
Lorenzo Colitti <lorenzo@google.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] selftests/bpf: fix broken build of test_maps
Date: Sat, 21 Oct 2017 10:23:08 +0200 [thread overview]
Message-ID: <59EB03EC.9060002@iogearbox.net> (raw)
In-Reply-To: <20171021062533.2090015-1-ast@fb.com>
On 10/21/2017 08:25 AM, Alexei Starovoitov wrote:
> fix broken tests
>
> Fixes: e043325b3087 ("bpf: Add tests for eBPF file mode")
> Fixes: 6e71b04a8224 ("bpf: Add file mode configuration into bpf maps")
> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
> ---
> Chenbo,
>
> this was very broken patch submission.
> Please make sure to actually compile your tests before sending patches.
Urks, and still after that many rounds ...
Acked-by: Daniel Borkmann <daniel@iogearbox.net>
prev parent reply other threads:[~2017-10-21 8:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-21 6:25 [PATCH net-next] selftests/bpf: fix broken build of test_maps Alexei Starovoitov
2017-10-21 8:23 ` 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=59EB03EC.9060002@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@fb.com \
--cc=davem@davemloft.net \
--cc=fengc@google.com \
--cc=lorenzo@google.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).