From: Jarod Wilson <jarod@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: Re: sha384 self-test failure oddity
Date: Tue, 2 Jun 2009 15:41:34 -0400 [thread overview]
Message-ID: <200906021541.34774.jarod@redhat.com> (raw)
In-Reply-To: <20090602132038.GA29795@gondor.apana.org.au>
On Tuesday 02 June 2009 09:20:38 Herbert Xu wrote:
> On Tue, Jun 02, 2009 at 09:01:42AM -0400, Jarod Wilson wrote:
> >
> > > I can't reproduce this with 2.6.30-rc7.
> >
> > I'll rebase my cryptodev tree to 2.6.30-rcX and see if I can still
> > reproduce the problem.
>
> I just rebased cryptodev against 2.6.30-rc7 today so please let
> me know whether you can still reproduce it with cryptodev.
Still happens after the rebase. Kernel config here, if it helps:
http://jwilson.fedorapeople.org/misc/cryptodev-2.6-config
--
Jarod Wilson
jarod@redhat.com
next prev parent reply other threads:[~2009-06-02 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 18:35 sha384 self-test failure oddity Jarod Wilson
2009-06-02 5:10 ` Herbert Xu
2009-06-02 13:01 ` Jarod Wilson
2009-06-02 13:20 ` Herbert Xu
2009-06-02 19:41 ` Jarod Wilson [this message]
2009-06-16 11:22 ` Herbert Xu
2009-06-16 12:39 ` Jarod Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200906021541.34774.jarod@redhat.com \
--to=jarod@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.