netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jbenc@redhat.com
Cc: netdev@vger.kernel.org, tgraf@suug.ch, pshelar@ovn.org,
	simon.horman@netronome.com
Subject: Re: [PATCH net-next 0/3] gre: receive also TEB packets for lwtunnels
Date: Wed, 04 May 2016 14:11:50 -0400 (EDT)	[thread overview]
Message-ID: <20160504.141150.1172239925654406356.davem@davemloft.net> (raw)
In-Reply-To: <cover.1462286214.git.jbenc@redhat.com>

From: Jiri Benc <jbenc@redhat.com>
Date: Tue,  3 May 2016 17:10:05 +0200

> NOTE: this patchset needs net merged to net-next.

Noted.

> This allows lwtunnel users to get also packets with ETH_P_TEB protocol
> specified in GRE header through an ipgre interface. There's really nothing
> special about these packets in the case of lwtunnels - it's just an inner
> protocol like any other. The only complications stem from keeping
> compatibility with other uses of GRE.
> 
> This will be used by openvswitch to support eth_push and eth_pop actions.
> I'd also like to see tc support for lwtunnels (this feature included) in the
> future.
> 
> The first patch is not directly related and can be submitted standalone if
> needed.

Series applied, thanks Jiri.

      parent reply	other threads:[~2016-05-04 18:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-03 15:10 [PATCH net-next 0/3] gre: receive also TEB packets for lwtunnels Jiri Benc
2016-05-03 15:10 ` [PATCH net-next 1/3] gre: remove superfluous pskb_may_pull Jiri Benc
2016-05-03 15:10 ` [PATCH net-next 2/3] gre: move iptunnel_pull_header down to ipgre_rcv Jiri Benc
2016-05-03 15:10 ` [PATCH net-next 3/3] gre: receive also TEB packets for lwtunnels Jiri Benc
2016-05-04  7:52 ` [PATCH net-next 0/3] " Simon Horman
2016-05-04 18:11 ` David Miller [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=20160504.141150.1172239925654406356.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jbenc@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@ovn.org \
    --cc=simon.horman@netronome.com \
    --cc=tgraf@suug.ch \
    /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).