From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Miller <davem@davemloft.net>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Steffen Klassert <steffen.klassert@secunet.com>,
<netdev@vger.kernel.org>
Subject: pull request (net-next): ipsec-next 2018-12-20
Date: Thu, 20 Dec 2018 09:20:47 +0100 [thread overview]
Message-ID: <20181220082049.18029-1-steffen.klassert@secunet.com> (raw)
Two last patches for this release cycle:
1) Remove an unused variable in xfrm_policy_lookup_bytype().
From YueHaibing.
2) Fix possible infinite loop in __xfrm6_tunnel_alloc_spi().
Also from YueHaibing.
Please pull or let me know if there are problems.
Thanks!
The following changes since commit 33f18c96afdf4da20014f834874e2820ee880cde:
net: ethernet: don't set phylib state CHANGELINK in drivers (2018-12-18 22:07:20 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git master
for you to fetch changes up to fa89a4593b927b3f59c3b69379f31d3b22272e4e:
xfrm6_tunnel: Fix spi check in __xfrm6_tunnel_alloc_spi (2018-12-19 12:33:17 +0100)
----------------------------------------------------------------
YueHaibing (2):
xfrm: policy: remove set but not used variable 'priority'
xfrm6_tunnel: Fix spi check in __xfrm6_tunnel_alloc_spi
net/ipv6/xfrm6_tunnel.c | 3 +++
net/xfrm/xfrm_policy.c | 3 ---
2 files changed, 3 insertions(+), 3 deletions(-)
next reply other threads:[~2018-12-20 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 8:20 Steffen Klassert [this message]
2018-12-20 8:20 ` [PATCH 1/2] xfrm: policy: remove set but not used variable 'priority' Steffen Klassert
2018-12-20 8:20 ` [PATCH 2/2] xfrm6_tunnel: Fix spi check in __xfrm6_tunnel_alloc_spi Steffen Klassert
2018-12-20 16:22 ` pull request (net-next): ipsec-next 2018-12-20 David Miller
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=20181220082049.18029-1-steffen.klassert@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
/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).