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-06-23
Date: Fri, 23 Jun 2017 14:18:19 -0400 (EDT) [thread overview]
Message-ID: <20170623.141819.1988940567947681365.davem@davemloft.net> (raw)
In-Reply-To: <1498207110-22520-1-git-send-email-steffen.klassert@secunet.com>
From: Steffen Klassert <steffen.klassert@secunet.com>
Date: Fri, 23 Jun 2017 10:38:24 +0200
> 1) Use memdup_user to spmlify xfrm_user_policy.
> From Geliang Tang.
>
> 2) Make xfrm_dev_register static to silence a sparse warning.
> From Wei Yongjun.
>
> 3) Use crypto_memneq to check the ICV in the AH protocol.
> From Sabrina Dubroca.
>
> 4) Remove some unused variables in esp6.
> From Stephen Hemminger.
>
> 5) Extend XFRM MIGRATE to allow to change the UDP encapsulation port.
> From Antony Antony.
>
> 6) Include the UDP encapsulation port to km_migrate announcements.
> From Antony Antony.
>
> Please pull or let me know if there are problems.
Pulled, thank you very much.
prev parent reply other threads:[~2017-06-23 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 8:38 pull request (net-next): ipsec-next 2017-06-23 Steffen Klassert
2017-06-23 8:38 ` [PATCH 1/6] xfrm: use memdup_user Steffen Klassert
2017-06-23 8:38 ` [PATCH 2/6] xfrm: Make function xfrm_dev_register static Steffen Klassert
2017-06-23 8:38 ` [PATCH 3/6] ah: use crypto_memneq to check the ICV Steffen Klassert
2017-06-23 8:38 ` [PATCH 4/6] ipv6: remove unused variables in esp6 Steffen Klassert
2017-06-23 8:38 ` [PATCH 5/6] xfrm: extend MIGRATE with UDP encapsulation port Steffen Klassert
2017-06-23 8:38 ` [PATCH 6/6] xfrm: add UDP encapsulation port in migrate message Steffen Klassert
2017-06-23 18:18 ` 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=20170623.141819.1988940567947681365.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).