From: David Ahern <dsahern@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Peter Oskolkov <posk@google.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
netdev@vger.kernel.org, Peter Oskolkov <posk@posk.io>,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH bpf-next v9 7/7] selftests: bpf: add test_lwt_ip_encap selftest
Date: Mon, 11 Feb 2019 21:40:18 -0700 [thread overview]
Message-ID: <da9a2e62-a83f-f192-5c29-03d73317f2e5@gmail.com> (raw)
In-Reply-To: <20190212043938.xln5tkoerpovvkcl@ast-mbp>
On 2/11/19 9:39 PM, Alexei Starovoitov wrote:
> This needs one more rebase on top of Jiong's makefile changes.
> Other than this it looks great.
> Thanks!
needs more than that. just sent comments about patch 5.
next prev parent reply other threads:[~2019-02-12 4:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 0:42 [PATCH bpf-next v9 0/7] bpf: add BPF_LWT_ENCAP_IP option to bpf_lwt_push_encap Peter Oskolkov
2019-02-12 0:42 ` [PATCH bpf-next v9 1/7] bpf: add plumbing for BPF_LWT_ENCAP_IP in bpf_lwt_push_encap Peter Oskolkov
2019-02-12 0:42 ` [PATCH bpf-next v9 2/7] bpf: implement BPF_LWT_ENCAP_IP mode " Peter Oskolkov
2019-02-12 0:42 ` [PATCH bpf-next v9 3/7] bpf: handle GSO " Peter Oskolkov
2019-02-12 0:42 ` [PATCH bpf-next v9 4/7] ipv6_stub: add ipv6_route_input stub/proxy Peter Oskolkov
2019-02-12 0:42 ` [PATCH bpf-next v9 5/7] bpf: add handling of BPF_LWT_REROUTE to lwt_bpf.c Peter Oskolkov
2019-02-12 4:39 ` David Ahern
2019-02-12 0:42 ` [PATCH bpf-next v9 6/7] bpf: sync <kdir>/include/.../bpf.h with tools/include/.../bpf.h Peter Oskolkov
2019-02-12 0:42 ` [PATCH bpf-next v9 7/7] selftests: bpf: add test_lwt_ip_encap selftest Peter Oskolkov
2019-02-12 4:39 ` Alexei Starovoitov
2019-02-12 4:40 ` David Ahern [this message]
2019-02-12 4:41 ` 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=da9a2e62-a83f-f192-5c29-03d73317f2e5@gmail.com \
--to=dsahern@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=posk@google.com \
--cc=posk@posk.io \
--cc=willemb@google.com \
/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).