From: David Miller <davem@davemloft.net>
To: david.lebrun@uclouvain.be
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/5] net: updates for IPv6 Segment Routing
Date: Fri, 25 Aug 2017 17:10:47 -0700 (PDT) [thread overview]
Message-ID: <20170825.171047.1935113010419428511.davem@davemloft.net> (raw)
In-Reply-To: <20170825075648.5061-1-david.lebrun@uclouvain.be>
From: David Lebrun <david.lebrun@uclouvain.be>
Date: Fri, 25 Aug 2017 09:56:43 +0200
> v2: seg6_lwt_headroom() is not relevant for lwtunnel_input_redirect()
> use cases, and L2ENCAP only uses this redirection. Fix incoherence
> between arbitrary MAC header size support and fixed headroom
> computation by setting only LWTUNNEL_STATE_INPUT_REDIRECT for L2ENCAP
> mode.
>
> This patch series provides several updates for the SRv6 implementation. The
> first patch leverages the existing infrastructure to support encapsulation
> of IPv4 packets. The second patch implements the T.Encaps.L2 SR function,
> enabling to encapsulate an L2 Ethernet frame within an IPv6+SRH packet.
> The last three patches update the seg6local lightweight tunnel, and mainly
> implement four new actions: End.T, End.DX2, End.DX4 and End.DT6.
Series applied, thanks.
prev parent reply other threads:[~2017-08-26 0:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 7:56 [PATCH net-next v2 0/5] net: updates for IPv6 Segment Routing David Lebrun
2017-08-25 7:56 ` [PATCH net-next v2 1/5] ipv6: sr: add support for ip4ip6 encapsulation David Lebrun
2017-08-25 7:56 ` [PATCH net-next v2 2/5] ipv6: sr: add support for encapsulation of L2 frames David Lebrun
2017-08-25 7:56 ` [PATCH net-next v2 3/5] ipv6: sr: enforce IPv6 packets for seg6local lwt David Lebrun
2017-08-25 7:56 ` [PATCH net-next v2 4/5] ipv6: sr: add helper functions for seg6local David Lebrun
2017-08-25 7:58 ` [PATCH net-next v2 5/5] ipv6: sr: implement additional seg6local actions David Lebrun
2017-08-26 0:10 ` 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=20170825.171047.1935113010419428511.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=david.lebrun@uclouvain.be \
--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).