From: David Miller Subject: Re: [RFC PATCH 0/3] Make rfc3686 template work with asynchronous block ciphers Date: Fri, 28 Dec 2012 15:23:11 -0800 (PST) Message-ID: <20121228.152311.290755667605168896.davem@davemloft.net> References: <20121228100448.11073.25546.stgit@localhost6.localdomain6> <20121228224248.GA29448@gondor.apana.org.au> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: jussi.kivilinna@mbnet.fi, linux-crypto@vger.kernel.org, steffen.klassert@secunet.com, netdev@vger.kernel.org To: herbert@gondor.apana.org.au Return-path: Received: from shards.monkeyblade.net ([149.20.54.216]:55925 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755051Ab2L1XXM (ORCPT ); Fri, 28 Dec 2012 18:23:12 -0500 In-Reply-To: <20121228224248.GA29448@gondor.apana.org.au> Sender: linux-crypto-owner@vger.kernel.org List-ID: From: Herbert Xu Date: Sat, 29 Dec 2012 09:42:49 +1100 > 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. Better yet, Steffen's IPSEC tree :-)