netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 2013-10-18
Date: Fri, 18 Oct 2013 13:52:10 -0400 (EDT)	[thread overview]
Message-ID: <20131018.135210.2168457289330865474.davem@davemloft.net> (raw)
In-Reply-To: <1382085730-3415-1-git-send-email-steffen.klassert@secunet.com>

From: Steffen Klassert <steffen.klassert@secunet.com>
Date: Fri, 18 Oct 2013 10:42:06 +0200

> 1) Don't use a wildcard SA if a more precise one is in acquire state,
>    from Fan Du.
> 
> 2) Simplify the SA lookup when using wildcard source. We need to check
>    only the destination in this case, from Fan Du.
> 
> 3) Add a receive path hook for IPsec virtual tunnel interfaces
>    to xfrm6_mode_tunnel.
> 
> 4) Add support for IPsec virtual tunnel interfaces to ipv6.
> 
> Please pull or let me know if there are problems.

Pulled, thanks Steffen.

      parent reply	other threads:[~2013-10-18 17:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18  8:42 pull request (net-next): ipsec-next 2013-10-18 Steffen Klassert
2013-10-18  8:42 ` [PATCH 1/4] xfrm: Force SA to be lookup again if SA in acquire state Steffen Klassert
2013-10-18  8:42 ` [PATCH 2/4] xfrm: Simplify SA looking up when using wildcard source Steffen Klassert
2013-10-18  8:42 ` [PATCH 3/4] ipv6: Add a receive path hook for vti6 in xfrm6_mode_tunnel Steffen Klassert
2013-10-18  8:42 ` [PATCH 4/4] ipv6: Add support for IPsec virtual tunnel interfaces Steffen Klassert
2013-10-18 17:52 ` 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=20131018.135210.2168457289330865474.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).