All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Fruhwirth Clemens <clemens-dated-1056963973.bf26@endorphin.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Initial Vector Fix for loop.c.
Date: Fri, 20 Jun 2003 02:23:08 -0700	[thread overview]
Message-ID: <20030620022308.2afa8142.akpm@digeo.com> (raw)
In-Reply-To: <20030620090612.GA1322@ghanima.endorphin.org>

Fruhwirth Clemens <clemens-dated-1056963973.bf26@endorphin.org> wrote:
>
> If this bug is fixed, we can go ahead and add cryptoloop which is ready and
>  tested.

Does it use the crypto framework which is present in the 2.5 kernel?

If it does not then the cryptoloop implementation which you mention
is inappropriate for inclusion.

If it does then it would be nice to see the full patchset.

  reply	other threads:[~2003-06-20  9:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-20  9:06 [PATCH] Initial Vector Fix for loop.c Fruhwirth Clemens
2003-06-20  9:23 ` Andrew Morton [this message]
     [not found] <20030620090612.GA1322@ghanima.endorphin.org.suse.lists.linux.kernel>
2003-06-20  9:30 ` Andi Kleen
2003-06-20 10:14   ` Fruhwirth Clemens
2003-06-20 10:24     ` Andi Kleen
2003-06-20 10:33       ` Fruhwirth Clemens
2003-06-20 10:35       ` Jörn Engel
2003-06-20 10:49         ` Andi Kleen
2003-06-20 10:52           ` Andi Kleen
2003-06-20 11:15           ` Fruhwirth Clemens
2003-06-20 10:51         ` Fruhwirth Clemens
2003-06-20 11:03           ` Jörn Engel
2003-06-21  2:18           ` Jan Rychter
2003-06-24 18:22       ` Bill Davidsen
2003-06-20 17:56   ` Andrew Morton
2003-06-20 18:14     ` David S. Miller
2003-06-20 19:04       ` Andries Brouwer
  -- strict thread matches above, loose matches on Subject: below --
2003-06-20 13:38 Fruhwirth Clemens

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=20030620022308.2afa8142.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=clemens-dated-1056963973.bf26@endorphin.org \
    --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 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.