From: Jiri Benc <jbenc@redhat.com>
To: Pravin Shelar <pshelar@nicira.com>
Cc: netdev <netdev@vger.kernel.org>,
"dev@openvswitch.org" <dev@openvswitch.org>,
Jesse Gross <jesse@nicira.com>
Subject: Re: [PATCH net-next v2 4/4] openvswitch: IPv6 support for ovs_tunnel_get_egress_info
Date: Fri, 2 Oct 2015 08:00:41 +0200 [thread overview]
Message-ID: <20151002080041.52017d26@griffin> (raw)
In-Reply-To: <CALnjE+o-ou=Vpv8_e20-CyRMA62ceGiDOZuSaRU9Qwb_WBBP8Q@mail.gmail.com>
On Thu, 1 Oct 2015 17:11:56 -0700, Pravin Shelar wrote:
> I dont see point of adding this code when IPv6 sampling not support by
> the patch series.
It was requested by Jesse:
http://article.gmane.org/gmane.linux.network/380348
I don't mind leaving this and the previous patch out, it's actually
what I did in v1.
Jiri
--
Jiri Benc
next prev parent reply other threads:[~2015-10-02 6:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 14:44 [PATCH net-next v2 0/4] openvswitch: add IPv6 tunneling support Jiri Benc
2015-10-01 14:44 ` [PATCH net-next v2 1/4] openvswitch: add tunnel protocol to sw_flow_key Jiri Benc
2015-10-02 0:10 ` Pravin Shelar
2015-10-01 14:44 ` [PATCH net-next v2 2/4] openvswitch: netlink attributes for IPv6 tunneling Jiri Benc
2015-10-02 0:10 ` Pravin Shelar
2015-10-01 14:44 ` [PATCH net-next v2 3/4] ip_tunnels: introduce ip6_tunnel_key_init Jiri Benc
2015-10-02 0:11 ` Pravin Shelar
2015-10-02 5:58 ` Jiri Benc
2015-10-01 14:44 ` [PATCH net-next v2 4/4] openvswitch: IPv6 support for ovs_tunnel_get_egress_info Jiri Benc
2015-10-02 0:11 ` Pravin Shelar
2015-10-02 6:00 ` Jiri Benc [this message]
2015-10-02 19:32 ` Pravin Shelar
[not found] ` <CALnjE+qn7PrEYxKZ6c03-Bz63BcROVuqmwdp8sqi2eXvxY-yeg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-03 0:57 ` Jesse Gross
2015-10-05 18:05 ` Pravin Shelar
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=20151002080041.52017d26@griffin \
--to=jbenc@redhat.com \
--cc=dev@openvswitch.org \
--cc=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.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.