From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steffen Klassert Subject: Re: [PATCHv2 net-next 0/3] Small IPsec fix Date: Fri, 8 Nov 2013 12:54:59 +0100 Message-ID: <20131108115459.GT31491@secunet.com> References: <1383817670-5783-1-git-send-email-fan.du@windriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: herbert@gondor.hengli.com.au, davem@davemloft.net, netdev@vger.kernel.org To: Fan Du Return-path: Received: from a.mx.secunet.com ([195.81.216.161]:38294 "EHLO a.mx.secunet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753166Ab3KHLzB (ORCPT ); Fri, 8 Nov 2013 06:55:01 -0500 Content-Disposition: inline In-Reply-To: <1383817670-5783-1-git-send-email-fan.du@windriver.com> Sender: netdev-owner@vger.kernel.org List-ID: 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!