On 24 November 2015 at 10:54, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> wrote: > Andrew Zaborowski <andrew.zaborowski@xxxxxxxxx> wrote: >> Expose crypto_akcipher_type like other crypto types are exposed to be >> used from outside akcipher.c. Add a struct akcipher_instance similar to >> aead_instance with just the right size for an akcipher template >> instance, and two macros for converting to/from crypto_instance. > > You're still doing some things in the old way. With new templates, > you shouldn't need to export the crypto type at all. Please look > at how AEAD does it. It doesn't need to export crypto_aead_type but instead needs to export crypto_aead_grab and aead_register_instance. I'll add those for akcipher and resend then. Would there be any point defining a crypto_akcipher_spawn following the AEAD pattern? Best regards -- 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
