From: Mathias Krause <minipli@googlemail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org,
Mathias Krause <minipli@googlemail.com>
Subject: [PATCH 0/6] crypto: module alias fixes
Date: Sun, 11 Jan 2015 18:17:41 +0100 [thread overview]
Message-ID: <1420996667-31693-1-git-send-email-minipli@googlemail.com> (raw)
Hi Herbert,
this series is a follow up to commit 5d26a105b5a7 ("crypto: prefix
module autoloading with "crypto-""). In patch 1 it adds the required
MODULE_ALIAS_CRYPTO annotation where needed to bring back automatic
crypto module loading. Namely, modules that have a file name matching
the cipher they implement still need the MODULE_ALIAS_CRYPTO()
annotation. Otherwise they won't get loaded.
Patches 2 to 6 fix bogus module descriptions or aliases with the
exception of patch 4 which adds a missing crypto module alias.
At least patch 1 should go to crypto-2.6 to not regress the crypto API
for v3.19 in regard to automatic module loading.
The others are probably safe to apply, too.
Please apply!
Thanks,
Mathias Krause (6):
crypto: add missing crypto module aliases
crypto: sparc64/aes - fix module description
crypto: sparc64/camellia - fix module alias
crypto: sparc64/des - add "des3_ede" module alias
crypto: sparc64/md5 - fix module description
crypto: x86/des3_ede - drop bogus module aliases
arch/powerpc/crypto/sha1.c | 1 +
arch/sparc/crypto/aes_glue.c | 2 +-
arch/sparc/crypto/camellia_glue.c | 2 +-
arch/sparc/crypto/des_glue.c | 1 +
arch/sparc/crypto/md5_glue.c | 2 +-
arch/x86/crypto/des3_ede_glue.c | 2 --
arch/x86/crypto/sha-mb/sha1_mb.c | 2 +-
crypto/aes_generic.c | 1 +
crypto/ansi_cprng.c | 1 +
crypto/blowfish_generic.c | 1 +
crypto/camellia_generic.c | 1 +
crypto/cast5_generic.c | 1 +
crypto/cast6_generic.c | 1 +
crypto/crc32c_generic.c | 1 +
crypto/crct10dif_generic.c | 1 +
crypto/des_generic.c | 7 ++++---
crypto/ghash-generic.c | 1 +
crypto/krng.c | 1 +
crypto/salsa20_generic.c | 1 +
crypto/serpent_generic.c | 1 +
crypto/sha1_generic.c | 1 +
crypto/sha256_generic.c | 2 ++
crypto/sha512_generic.c | 2 ++
crypto/tea.c | 1 +
crypto/tgr192.c | 1 +
crypto/twofish_generic.c | 1 +
crypto/wp512.c | 1 +
27 files changed, 31 insertions(+), 9 deletions(-)
--
1.7.10.4
next reply other threads:[~2015-01-11 17:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-11 17:17 Mathias Krause [this message]
2015-01-11 17:17 ` [PATCH 1/6] crypto: add missing crypto module aliases Mathias Krause
2015-01-13 15:36 ` Kees Cook
2015-01-11 17:17 ` [PATCH 2/6] crypto: sparc64/aes - fix module description Mathias Krause
2015-01-11 17:57 ` David Miller
2015-01-11 17:17 ` [PATCH 3/6] crypto: sparc64/camellia - fix module alias Mathias Krause
2015-01-11 17:57 ` David Miller
2015-01-11 17:17 ` [PATCH 4/6] crypto: sparc64/des - add "des3_ede" " Mathias Krause
2015-01-11 17:57 ` David Miller
2015-01-11 17:17 ` [PATCH 5/6] crypto: sparc64/md5 - fix module description Mathias Krause
2015-01-11 17:57 ` David Miller
2015-01-11 17:17 ` [PATCH 6/6] crypto: x86/des3_ede - drop bogus module aliases Mathias Krause
2015-01-13 11:32 ` [PATCH 0/6] crypto: module alias fixes Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1420996667-31693-1-git-send-email-minipli@googlemail.com \
--to=minipli@googlemail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox