From: Jiri Benc <jbenc@redhat.com>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
davem@davemloft.net, Roopa Prabhu <roopa@cumulusnetworks.com>,
jiri@resnulli.us, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
oss-drivers@netronome.com, netdev@vger.kernel.org,
Pieter Jansen van Vuuren <pieter.jansenvanvuuren@netronome.com>
Subject: Re: [PATCH net-next v2 3/4] net: check tunnel option type in tunnel flags
Date: Fri, 29 Jun 2018 11:06:01 +0200 [thread overview]
Message-ID: <20180629110601.1a4463d1@redhat.com> (raw)
In-Reply-To: <20180628100536.71e5ca59@cakuba.netronome.com>
On Thu, 28 Jun 2018 10:05:36 -0700, Jakub Kicinski wrote:
> Can we take this as a follow up through the bpf-next tree or do you
> want us to respin as part of this set?
I think BPF is a separate issue.
Jiri
next prev parent reply other threads:[~2018-06-29 9:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 4:39 [PATCH net-next v2 0/4] net: Geneve options support for TC act_tunnel_key Jakub Kicinski
2018-06-27 4:39 ` [PATCH net-next v2 1/4] net/sched: act_tunnel_key: disambiguate metadata dst error cases Jakub Kicinski
2018-06-27 4:39 ` [PATCH net-next v2 2/4] net/sched: act_tunnel_key: add extended ack support Jakub Kicinski
2018-06-27 4:39 ` [PATCH net-next v2 3/4] net: check tunnel option type in tunnel flags Jakub Kicinski
2018-06-27 9:49 ` Daniel Borkmann
2018-06-28 7:42 ` Jiri Benc
2018-06-28 16:54 ` Jakub Kicinski
2018-06-28 17:01 ` Jiri Benc
2018-06-28 17:05 ` Jakub Kicinski
2018-06-29 9:06 ` Jiri Benc [this message]
2018-06-29 7:04 ` Daniel Borkmann
2018-06-29 17:01 ` Jakub Kicinski
2018-06-30 8:47 ` Daniel Borkmann
2018-06-27 4:39 ` [PATCH net-next v2 4/4] net/sched: add tunnel option support to act_tunnel_key Jakub Kicinski
2018-06-29 14:51 ` [PATCH net-next v2 0/4] net: Geneve options support for TC act_tunnel_key David Miller
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=20180629110601.1a4463d1@redhat.com \
--to=jbenc@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=pieter.jansenvanvuuren@netronome.com \
--cc=roopa@cumulusnetworks.com \
--cc=xiyou.wangcong@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.