From: alastair@au1.ibm.com
To: mpe@ellerman.id.au
Cc: benh@kernel.crashing.org, paulus@samba.org,
herbert@gondor.apana.org.au, davem@davemloft.net,
linuxppc-dev@lists.ozlabs.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Alastair D'Silva" <alastair@d-silva.org>
Subject: [PATCH 0/2] Automatically load the vmx_crypto module if supported
Date: Wed, 13 Jul 2016 15:47:16 +1000 [thread overview]
Message-ID: <1468388840-12068-1-git-send-email-alastair@au1.ibm.com> (raw)
From: Alastair D'Silva <alastair@d-silva.org>
This series allows the vmx_crypto module to be detected and automatically
loaded via UDEV if the CPU supports the vector crypto feature.
Alastair D'Silva (2):
powerpc: Add module autoloading based on CPU features
crypto: vmx - Convert to CPU feature based module autoloading
arch/powerpc/Kconfig | 1 +
arch/powerpc/include/asm/cpufeature.h | 70 +++++++++++++++++++++++++++++++++++
drivers/crypto/vmx/Kconfig | 2 +-
drivers/crypto/vmx/vmx.c | 6 +--
4 files changed, 74 insertions(+), 5 deletions(-)
create mode 100644 arch/powerpc/include/asm/cpufeature.h
--
2.7.4
next reply other threads:[~2016-07-13 5:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 5:47 alastair [this message]
2016-07-13 5:47 ` [PATCH 1/2] Allow drivers to be autoloaded alastair
2016-07-13 5:47 ` [PATCH 1/2] powerpc: Add module autoloading based on CPU features alastair
2016-07-19 1:04 ` Michael Ellerman
2016-07-13 5:47 ` [PATCH 2/2] Automatically load the vmx_crypto module if supported alastair
2016-07-13 5:47 ` [PATCH 2/2] crypto: vmx - Convert to CPU feature based module autoloading alastair
2016-07-13 5:54 ` [PATCH 0/2] Automatically load the vmx_crypto module if supported Alastair D'Silva
2016-07-14 3:34 ` Balbir Singh
2016-07-18 10:22 ` Herbert Xu
2016-07-19 1:01 ` Michael Ellerman
2016-07-19 3:59 ` Herbert Xu
2016-07-19 9:13 ` Michael Ellerman
2016-07-19 9:52 ` 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=1468388840-12068-1-git-send-email-alastair@au1.ibm.com \
--to=alastair@au1.ibm.com \
--cc=alastair@d-silva.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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).