"Leisner, Martin" wrote: > In this stanza: > extern void loop_compute_sector_iv(sector_t, u_int32_t *); > EXPORT_SYMBOL(loop_compute_sector_iv); > extern void loop_compute_md5_iv_v3(sector_t, u_int32_t *, u_int32_t *); > EXPORT_SYMBOL(loop_compute_md5_iv_v3); > extern void loop_compute_md5_iv(sector_t, u_int32_t *, u_int32_t *); > EXPORT_SYMBOL(loop_compute_md5_iv); > extern void md5_transform_CPUbyteorder(u_int32_t *, u_int32_t const *); > EXPORT_SYMBOL(md5_transform_CPUbyteorder); > extern void md5_transform_CPUbyteorder_C(u_int32_t *, u_int32_t const > *); > EXPORT_SYMBOL(md5_transform_CPUbyteorder_C); > > Isn't it more standard if the EXPORT_SYMBOL appear next to the function > definition? Yes, that would be more "standard". But in this case those symbols are not exported in all kernel versions. That is why they are in kernel version specific file. > Why would they be exported? Who uses them other than the loopAES > module? Other loop ciphers may use them. (loop_twofish & co) -- Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
