On Sun, Sep 02, 2007 at 02:39:15AM +0530, Satyam Sharma wrote: > > Tangential, but I've often wondered what are the upsides of keeping > CONFIG_CRYPTO_ALGAPI as a separate config option in the first place? Every > single item in crypto/ ends up "select"ing it (directly or transitively) > so it makes all sense to just do away with it and keep it == CONFIG_CRYPTO > in the Makefile, thusly: NACK. ALGAPI exists so that it can be built as a module, as opposed to CRYPTO which is always built-in. It's already invisible to the user so I don't see why you have a problem with it. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt - To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
