From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: linux-crypto@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [3/7] [CRYPTO] api: Split out low-level API
Date: Sat, 05 Aug 2006 01:49:58 -0700 (PDT) [thread overview]
Message-ID: <20060805.014958.26300600.davem@davemloft.net> (raw)
In-Reply-To: <20060804133426.GB12832@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Fri, 4 Aug 2006 23:34:26 +1000
> [CRYPTO] api: Split out low-level API
>
> The crypto API is made up of the part facing users such as IPsec and the
> low-level part which is used by cryptographic entities such as algorithms.
> This patch splits out the latter so that the two APIs are more clearly
> delineated. As a bonus the low-level API can now be modularised if all
> algorithms are built as modules.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
This patch doesn't apply:
> config CRYPTO_MANAGER
> tristate "Cryptographic algorithm manager"
> - depends on CRYPTO
> + select CRYPTO_LOWAPI
> default m
> help
> Create default cryptographic template instantiations such as
There is no CRYPTO_MANAGER in my net-2.6.19 tree.
Are you patching against -mm or something like that?
I'm going to leave the rest of these patches until this
is resolved.
next prev parent reply other threads:[~2006-08-05 8:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 13:31 [1/7] [IPSEC]: Move linux/crypto.h inclusion out of net/xfrm.h Herbert Xu
2006-08-04 13:34 ` [3/7] [CRYPTO] api: Split out low-level API Herbert Xu
2006-08-05 8:49 ` David Miller [this message]
2006-08-05 10:06 ` Herbert Xu
2006-08-05 10:24 ` David Miller
2006-08-05 10:32 ` Herbert Xu
2006-08-05 10:36 ` Herbert Xu
2006-08-05 20:05 ` David Miller
2006-08-04 13:36 ` [5/7] [CRYPTO] api: Added asynchronous flag Herbert Xu
2006-08-04 13:38 ` [6/6] [CRYPTO] s390: Added missing driver name and priority Herbert Xu
2006-08-05 8:48 ` [1/7] [IPSEC]: Move linux/crypto.h inclusion out of net/xfrm.h David Miller
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=20060805.014958.26300600.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).