From: Herbert Xu Subject: Re: [RFC PATCH 0/3] Make rfc3686 template work with asynchronous block ciphers Date: Sat, 29 Dec 2012 09:42:49 +1100 Message-ID: <20121228224248.GA29448@gondor.apana.org.au> References: <20121228100448.11073.25546.stgit@localhost6.localdomain6> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-crypto@vger.kernel.org, Steffen Klassert , netdev@vger.kernel.org, "David S. Miller" To: Jussi Kivilinna Return-path: Content-Disposition: inline In-Reply-To: <20121228100448.11073.25546.stgit@localhost6.localdomain6> Sender: netdev-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org On Fri, Dec 28, 2012 at 12:04:48PM +0200, Jussi Kivilinna wrote: > I'm not sure how this patchset should be dealt with (should 1st patch go > through different tree than 2nd and 3rd?), so therefore it's RFC. > > Second patch makes rfc3686 template work with asynchronous block ciphers and > third patch changes aesni-intel to use this template. First patch fixed problem > in xfrm_algo found with help of 2nd and 3rd patches and without 1st patch > 2nd patch breaks aes-ctr with IPSEC. I think the easiest way is to have these patches go through Dave's tree. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt