From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au
Cc: linux-arm-kernel@lists.infradead.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: [PATCH 0/5] crypto: arm - enable module autoloading
Date: Sun, 21 May 2017 10:23:35 +0000 [thread overview]
Message-ID: <1495362220-30044-1-git-send-email-ard.biesheuvel@linaro.org> (raw)
Now that the prerequisite changes are in place, we can modify the
various accelerated crypto modules that use special instructions to
expose the CPU feature they depend on. This allows udev to autoload
the module at boot.
Ard Biesheuvel (5):
crypto: arm/aes-ce - enable module autoloading based on CPU feature
bits
crypto: arm/ghash-ce - enable module autoloading based on CPU feature
bits
crypto: arm/sha1-ce - enable module autoloading based on CPU feature
bits
crypto: arm/sha2-ce - enable module autoloading based on CPU feature
bits
crypto: arm/crc32 - enable module autoloading based on CPU feature
bits
arch/arm/crypto/aes-ce-glue.c | 6 ++----
arch/arm/crypto/crc32-ce-glue.c | 6 ++++++
arch/arm/crypto/ghash-ce-glue.c | 6 ++----
arch/arm/crypto/sha1-ce-glue.c | 5 ++---
arch/arm/crypto/sha2-ce-glue.c | 5 ++---
5 files changed, 14 insertions(+), 14 deletions(-)
--
2.7.4
next reply other threads:[~2017-05-21 10:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 10:23 Ard Biesheuvel [this message]
2017-05-21 10:23 ` [PATCH 1/5] crypto: arm/aes-ce - enable module autoloading based on CPU feature bits Ard Biesheuvel
2018-09-10 6:21 ` Stefan Agner
2018-09-10 7:01 ` Ard Biesheuvel
2018-09-13 6:24 ` Stefan Agner
2018-09-13 7:52 ` Ard Biesheuvel
2017-05-21 10:23 ` [PATCH 2/5] crypto: arm/ghash-ce " Ard Biesheuvel
2017-05-21 10:23 ` [PATCH 3/5] crypto: arm/sha1-ce " Ard Biesheuvel
2017-05-21 10:23 ` [PATCH 4/5] crypto: arm/sha2-ce " Ard Biesheuvel
2017-05-21 10:23 ` [PATCH 5/5] crypto: arm/crc32 " Ard Biesheuvel
2017-06-01 5:06 ` [PATCH 0/5] crypto: arm - enable module autoloading 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=1495362220-30044-1-git-send-email-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).