From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Alastair D'Silva <alastair@au1.ibm.com>
Cc: herbert@gondor.apana.org.au, linux-kernel@vger.kernel.org,
paulus@samba.org, linux-crypto@vger.kernel.org,
Alastair D'Silva <alastair@d-silva.org>,
linuxppc-dev@lists.ozlabs.org, davem@davemloft.net
Subject: Re: [V2,1/2] powerpc: Add module autoloading based on CPU features
Date: Fri, 22 Jul 2016 15:50:42 +1000 (AEST) [thread overview]
Message-ID: <3rwfrf1wwxz9t0F@ozlabs.org> (raw)
In-Reply-To: <1468901033-28996-2-git-send-email-alastair@au1.ibm.com>
On Tue, 2016-19-07 at 04:03:52 UTC, Alastair D'Silva wrote:
> From: Alastair D'Silva <alastair@d-silva.org>
>
> This patch provides the necessary infrastructure to allow drivers
> to be automatically loaded via UDEV. It implements the minimum
> required to be able to use module_cpu_feature_match to trigger
> the GENERIC_CPU_AUTOPROBE mechanisms.
>
> The features exposed are a mirror of the cpu_user_features
> (converted to an offset from a mask). This decision was made to
> ensure that the behavior between features for module loading and
> userspace are consistent.
>
> Signed-off-by: Alastair D'Silva <alastair@d-silva.org>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/4a1202765ddf4e5bb3143c0a85
cheers
next prev parent reply other threads:[~2016-07-22 5:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 4:03 [PATCH V2 0/2] Automatically load the vmx_crypto module if supported alastair
2016-07-19 4:03 ` [PATCH V2 1/2] powerpc: Add module autoloading based on CPU features alastair
2016-07-22 5:50 ` Michael Ellerman [this message]
2016-07-19 4:03 ` [PATCH V2 2/2] crypto: vmx - Convert to CPU feature based module autoloading alastair
2016-07-22 5:50 ` [V2, " Michael Ellerman
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=3rwfrf1wwxz9t0F@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=alastair@au1.ibm.com \
--cc=alastair@d-silva.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=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).