From: David Miller <davem@davemloft.net>
To: steffen.klassert@secunet.com
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: pull request (net-next): ipsec-next 2017-12-15
Date: Fri, 15 Dec 2017 11:10:47 -0500 (EST) [thread overview]
Message-ID: <20171215.111047.795959033073852375.davem@davemloft.net> (raw)
In-Reply-To: <20171215121952.20745-1-steffen.klassert@secunet.com>
From: Steffen Klassert <steffen.klassert@secunet.com>
Date: Fri, 15 Dec 2017 13:19:47 +0100
> 1) Currently we can add or update socket policies, but
> not clear them. Support clearing of socket policies
> too. From Lorenzo Colitti.
>
> 2) Add documentation for the xfrm device offload api.
> From Shannon Nelson.
>
> 3) Fix IPsec extended sequence numbers (ESN) for
> IPsec offloading. From Yossef Efraim.
>
> 4) xfrm_dev_state_add function returns success even for
> unsupported options, fix this to fail in such cases.
> From Yossef Efraim.
>
> 5) Remove a redundant xfrm_state assignment.
> From Aviv Heller.
>
> Please pull or let me know if there are problems.
Pulled, thank you Steffen.
prev parent reply other threads:[~2017-12-15 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 12:19 pull request (net-next): ipsec-next 2017-12-15 Steffen Klassert
2017-12-15 12:19 ` [PATCH 1/5] net: xfrm: allow clearing socket xfrm policies Steffen Klassert
2017-12-15 12:19 ` [PATCH 2/5] xfrm: add documentation for xfrm device offload api Steffen Klassert
2017-12-15 12:19 ` [PATCH 3/5] xfrm: Fix xfrm_replay_overflow_offload_esn Steffen Klassert
2017-12-15 12:19 ` [PATCH 4/5] xfrm: Fix xfrm_dev_state_add to fail for unsupported HW SA option Steffen Klassert
2017-12-15 12:19 ` [PATCH 5/5] xfrm: Remove redundant state assignment in xfrm_input() Steffen Klassert
2017-12-15 16: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=20171215.111047.795959033073852375.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/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).