public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jasper Spaans <jasper@vs19.net>
To: James Morris <jmorris@redhat.com>
Cc: linux-kernel@vger.kernel.org, ajgrothe@yahoo.com
Subject: Re: crypto algoritms failing?
Date: Fri, 28 Jan 2005 01:47:55 +0100	[thread overview]
Message-ID: <20050128004755.GA6676@spaans.vs19.net> (raw)
In-Reply-To: <Xine.LNX.4.44.0501271938070.7174-100000@thoron.boston.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 767 bytes --]

On Thu, Jan 27, 2005 at 07:38:43PM -0500, James Morris wrote:
> > Is this supposed to happen?
> 
> No.  What is your kernel version?

Current bitkeeper + latest swsusp2 patches and hostap driver, however, those
two don't come near touching the crypto stuff[1] so they're not really on my
suspect shortlist, but I'll see if I can find time to build a vanilla one
tomorrow (that is, without swsusp/hostap).. right now, it's time to sleep in
my local timezone..


Groet,
-- 
Jasper Spaans                                       http://jsp.vs19.net/
 01:40:46 up 10207 days, 17:27, 0 users, load average: 6.00 6.00 6.12

[1] hostap however does use some crypto algoritms, if I'm not mistaken, but
    its modules are not loaded in that stage of booting

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-01-28  0:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-27 23:30 crypto algoritms failing? Jasper Spaans
2005-01-28  0:38 ` James Morris
2005-01-28  0:47   ` Jasper Spaans [this message]
2005-01-28  1:43     ` James Morris
2005-01-28  9:14       ` Jasper Spaans
2005-01-28 10:55       ` Adrian Bunk
2005-01-28  1:49 ` Nigel Cunningham
2005-01-28  2:25   ` James Morris
2005-01-28  5:28     ` Nigel Cunningham

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=20050128004755.GA6676@spaans.vs19.net \
    --to=jasper@vs19.net \
    --cc=ajgrothe@yahoo.com \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox