From: Steffen Klassert <steffen.klassert@secunet.com>
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH ipsec-next v4 0/2] xfrm: add IPv6 encapsulation support for ESP over UDP and TCP
Date: Wed, 29 Apr 2020 09:52:07 +0200 [thread overview]
Message-ID: <20200429075207.GP13121@gauss3.secunet.de> (raw)
In-Reply-To: <cover.1588002010.git.sd@queasysnail.net>
On Mon, Apr 27, 2020 at 05:59:33PM +0200, Sabrina Dubroca wrote:
> This series adds IPv6 encapsulation of ESP over both UDP and TCP. In
> both cases, the code is very similar to the existing IPv4
> encapsulation implementation. The core espintcp code is almost
> entirely version-independent.
>
> v2: rebase on top of ipsec-next/master
> v3: really rebase this time
> v4: fix build warning when !_HAVE_ARCH_IPV6_CSUM
>
> Sabrina Dubroca (2):
> xfrm: add support for UDPv6 encapsulation of ESP
> xfrm: add IPv6 support for espintcp
Applied, thanks a lot Sabrina!
prev parent reply other threads:[~2020-04-29 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 15:59 [PATCH ipsec-next v4 0/2] xfrm: add IPv6 encapsulation support for ESP over UDP and TCP Sabrina Dubroca
2020-04-27 15:59 ` [PATCH ipsec-next v4 1/2] xfrm: add support for UDPv6 encapsulation of ESP Sabrina Dubroca
2020-04-27 15:59 ` [PATCH ipsec-next v4 2/2] xfrm: add IPv6 support for espintcp Sabrina Dubroca
2020-04-29 7:52 ` Steffen Klassert [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=20200429075207.GP13121@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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).