Steve French <smfrench@xxxxxxxxx> wrote: > There is not just the cifs md5 one (which has been around a long > time), but an md5_init (static) in crypto and the new one in rt. The > addition of the new one (rt md5_init) causes the build problem. It > would be nice if we could use the same md5 routines though ... last > time we checked the crypto one was not well suited for calculating > signatures as a network fs would do though. There is no longer any reason to have a custom md5 now that we have the new crypto_shash interface. 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-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
