From: Steffen Klassert <steffen.klassert@secunet.com>
To: Fan Du <fan.du@windriver.com>
Cc: herbert@gondor.hengli.com.au, davem@davemloft.net,
netdev@vger.kernel.org
Subject: Re: [PATCHv2 net-next 0/3] Small IPsec fix
Date: Fri, 8 Nov 2013 12:54:59 +0100 [thread overview]
Message-ID: <20131108115459.GT31491@secunet.com> (raw)
In-Reply-To: <1383817670-5783-1-git-send-email-fan.du@windriver.com>
On Thu, Nov 07, 2013 at 05:47:47PM +0800, Fan Du wrote:
> Hi
>
> This patchset made below modifications:
> - Fix setting policy index with "ip xfrm ... index=xx"
> which is currently broken
>
> - Using correct name space for home agent when migrating
> key info.
>
> - Put xfrm locks into per namespace to improve scalability.
>
> Changelog:
> v2:
> xfrm: Namespacify xfrm state/policy locks
> -Fix compile error when CONFIG_NET_NS is unset, thanks for the lovely build robot.
>
> Fan Du (3):
> xfrm: Try to honor policy index if it's supplied by user
> xfrm: Using the right namespace to migrate key info
> xfrm: Namespacify xfrm state/policy locks
Your patches are currently in the ipsec-next testing branch.
linux-next should not contain v3.14 material at the moment,
so I'll wait until after the merge window before I'm pushing
them to the master branch. No further action from your side
required.
Thanks, Fan!
next prev parent reply other threads:[~2013-11-08 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 9:47 [PATCHv2 net-next 0/3] Small IPsec fix Fan Du
2013-11-07 9:47 ` [PATCHv2 net-next 1/3] xfrm: Try to honor policy index if it's supplied by user Fan Du
2013-11-07 9:47 ` [PATCHv2 net-next 2/3] xfrm: Using the right namespace to migrate key info Fan Du
2013-11-07 9:47 ` [PATCHv2 net-next 3/3] xfrm: Namespacify xfrm state/policy locks Fan Du
2013-11-08 11:54 ` Steffen Klassert [this message]
2013-12-09 6:25 ` [PATCHv2 net-next 0/3] Small IPsec fix Steffen Klassert
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=20131108115459.GT31491@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=fan.du@windriver.com \
--cc=herbert@gondor.hengli.com.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).