From: Steffen Klassert <steffen.klassert@secunet.com>
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH ipsec-next v2 2/2] xfrm: add IPv6 support for espintcp
Date: Wed, 22 Apr 2020 13:05:41 +0200 [thread overview]
Message-ID: <20200422110541.GZ13121@gauss3.secunet.de> (raw)
In-Reply-To: <58b84b2af566138279348470b7ad27a8b9650372.1587484164.git.sd@queasysnail.net>
On Tue, Apr 21, 2020 at 06:04:23PM +0200, Sabrina Dubroca wrote:
> This extends espintcp to support IPv6, building on the existing code
> and the new UDPv6 encapsulation support. Most of the code is either
> reused directly (stream parser, ULP) or very similar to the IPv4
> variant (net/ipv6/esp6.c changes).
>
> The separation of config options for IPv4 and IPv6 espintcp requires a
> bit of Kconfig gymnastics to enable the core code.
>
> Signed-off-by: Sabrina Dubroca <sd@queasysnail.net>
This patch does not apply on top of patch 1/2:
git am -s ~/Mail/todo-ipsec-next
Applying: xfrm: add support for UDPv6 encapsulation of ESP
Applying: xfrm: add IPv6 support for espintcp
error: patch failed: net/xfrm/espintcp.c:416
error: net/xfrm/espintcp.c: patch does not apply
Patch failed at 0002 xfrm: add IPv6 support for espintcp
Can you please doublecheck this?
next prev parent reply other threads:[~2020-04-22 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 16:04 [PATCH ipsec-next v2 0/2] xfrm: add IPv6 encapsulation support for ESP over UDP and TCP Sabrina Dubroca
2020-04-21 16:04 ` [PATCH ipsec-next v2 1/2] xfrm: add support for UDPv6 encapsulation of ESP Sabrina Dubroca
2020-04-21 16:04 ` [PATCH ipsec-next v2 2/2] xfrm: add IPv6 support for espintcp Sabrina Dubroca
2020-04-22 11:05 ` Steffen Klassert [this message]
2020-04-22 15:31 ` Sabrina Dubroca
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=20200422110541.GZ13121@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