[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200730.144056.1854579189478441367.davem@davemloft.net>
Date: Thu, 30 Jul 2020 14:40:56 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: steffen.klassert@...unet.com
Cc: herbert@...dor.apana.org.au, netdev@...r.kernel.org
Subject: Re: pull request (net-next): ipsec-next 2020-07-30
From: Steffen Klassert <steffen.klassert@...unet.com>
Date: Thu, 30 Jul 2020 07:41:11 +0200
> Please note that I did the first time now --no-ff merges
> of my testing branch into the master branch to include
> the [PATCH 0/n] message of a patchset. Please let me
> know if this is desirable, or if I should do it any
> different.
It looks really nice, thanks for doing this.
> 1) Introduce a oseq-may-wrap flag to disable anti-replay
> protection for manually distributed ICVs as suggested
> in RFC 4303. From Petr Vaněk.
>
> 2) Patchset to fully support IPCOMP for vti4, vti6 and
> xfrm interfaces. From Xin Long.
>
> 3) Switch from a linear list to a hash list for xfrm interface
> lookups. From Eyal Birger.
>
> 4) Fixes to not register one xfrm(6)_tunnel object twice.
> From Xin Long.
>
> 5) Fix two compile errors that were introduced with the
> IPCOMP support for vti and xfrm interfaces.
> Also from Xin Long.
>
> 6) Make the policy hold queue work with VTI. This was
> forgotten when VTI was implemented.
>
> Please pull or let me know if there are problems.
...
> git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git master
Pulled, thank you!
Powered by blists - more mailing lists