On 06/26/2013 10:43 AM, bassamtabbara wrote: > this line broke our code that relies on CRYPTO_SHA2_256 having a value of 103 > in the enum. It also breaks compatibility with older versions of this > library. Can CRYPTO_SHA2_224 go at the bottom of the enum instead? > https://github.com/nmav/cryptodev-linux/commit/d87ab5584893d06a21fe7cbf6e052d6757f9aa91#commitcomment-3506697
Ouch. Indeed, this commit is problematic, sorry I didn't notice it. Unfortunately there is not much it can be done now. Even if I revert it, it would cause problems to others as it has been included in a release. Just consider the latest release as the proper ABI. regards, Nikos _______________________________________________ Cryptodev-linux-devel mailing list [email protected] https://mail.gna.org/listinfo/cryptodev-linux-devel
