From: Steffen Klassert <steffen.klassert@secunet.com>
Subject: Re: Bogus sha1 implementation in crypto4xx
Date: Wed, 15 Jul 2009 07:37:33 +0200
Message-ID: <20090715053733.GJ20288@secunet.com>
References: <20090714130600.GA11081@gondor.apana.org.au> <20090714134629.GI20288@secunet.com> <20090714144344.GB12160@gondor.apana.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: James Hsiao <jhsiao@amcc.com>, Shasi Pulijala <spulijala@amcc.com>,
	Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Return-path: <linux-crypto-owner@vger.kernel.org>
Received: from a.mx.secunet.com ([213.68.205.161]:41656 "EHLO a.mx.secunet.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751427AbZGOFey (ORCPT <rfc822;linux-crypto@vger.kernel.org>);
	Wed, 15 Jul 2009 01:34:54 -0400
Content-Disposition: inline
In-Reply-To: <20090714144344.GB12160@gondor.apana.org.au>
Sender: linux-crypto-owner@vger.kernel.org
List-ID: <linux-crypto.vger.kernel.org>

On Tue, Jul 14, 2009 at 10:43:44PM +0800, Herbert Xu wrote:
> 
> Sure, go ahead.  I'm still redoing the ahash infrastructure to
> properly support finup and export/import.
> 

Ok, for a moment I thought we both working at the same thing :)
I'll finalize my work and send everything in the next days.

Thanks for clarification.