From: Steffen Klassert Subject: Re: [PATCH 12/35] crypto: padlock - Switch sha to shash Date: Wed, 15 Jul 2009 12:47:36 +0200 Message-ID: <20090715104736.GO20288@secunet.com> References: <20090715071424.GA19023@gondor.apana.org.au> <20090715102818.GM20288@secunet.com> <20090715103025.GA21263@gondor.apana.org.au> <20090715103646.GN20288@secunet.com> <20090715103843.GA21411@gondor.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Linux Crypto Mailing List To: Herbert Xu Return-path: Received: from a.mx.secunet.com ([213.68.205.161]:44940 "EHLO a.mx.secunet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753398AbZGOKo5 (ORCPT ); Wed, 15 Jul 2009 06:44:57 -0400 Content-Disposition: inline In-Reply-To: <20090715103843.GA21411@gondor.apana.org.au> Sender: linux-crypto-owner@vger.kernel.org List-ID: On Wed, Jul 15, 2009 at 06:38:43PM +0800, Herbert Xu wrote: > On Wed, Jul 15, 2009 at 12:36:46PM +0200, Steffen Klassert wrote: > > > > It's 32-bit. > > One of my test systems had padlock enabled by chance. > > This should fix it. > Yes, it does. Thanks!