sparc64: Fix build with mix of modular vs. non-modular crypto drivers.
We tried linking in a single built object to hold the device table, but only works if all of the sparc64 crypto modules get built the same way (modular vs. non-modular). Just include the device ID stub into each driver source file so that the table gets compiled into the correct result in all cases. Reported-by:Meelis Roos <mroos@linux.ee> Signed-off-by:
David S. Miller <davem@davemloft.net>
Showing
- arch/sparc/crypto/Makefile 8 additions, 8 deletionsarch/sparc/crypto/Makefile
- arch/sparc/crypto/aes_glue.c 2 additions, 0 deletionsarch/sparc/crypto/aes_glue.c
- arch/sparc/crypto/camellia_glue.c 2 additions, 0 deletionsarch/sparc/crypto/camellia_glue.c
- arch/sparc/crypto/crc32c_glue.c 2 additions, 0 deletionsarch/sparc/crypto/crc32c_glue.c
- arch/sparc/crypto/des_glue.c 2 additions, 0 deletionsarch/sparc/crypto/des_glue.c
- arch/sparc/crypto/md5_glue.c 2 additions, 0 deletionsarch/sparc/crypto/md5_glue.c
- arch/sparc/crypto/sha1_glue.c 2 additions, 0 deletionsarch/sparc/crypto/sha1_glue.c
- arch/sparc/crypto/sha256_glue.c 2 additions, 0 deletionsarch/sparc/crypto/sha256_glue.c
- arch/sparc/crypto/sha512_glue.c 2 additions, 0 deletionsarch/sparc/crypto/sha512_glue.c
Please register or sign in to comment