From: Herbert Xu <herbert@gondor.apana.org.au>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: alastair@au1.ibm.com, benh@kernel.crashing.org, paulus@samba.org,
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: Re: [PATCH 0/2] Automatically load the vmx_crypto module if supported
Date: Tue, 19 Jul 2016 17:52:39 +0800 [thread overview]
Message-ID: <20160719095239.GA24167@gondor.apana.org.au> (raw)
In-Reply-To: <87poqa9eiz.fsf@@concordia.ellerman.id.au>
On Tue, Jul 19, 2016 at 07:13:24PM +1000, Michael Ellerman wrote:
>
> I'll assume patch 2 has your ack :)
Sure,
Acked-by: Herbert Xu <herbert@gondor.apana.org.au>
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2016-07-19 9:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 5:47 [PATCH 0/2] Automatically load the vmx_crypto module if supported alastair
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-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 1:01 ` Michael Ellerman
[not found] ` <87fur6phj0.fsf@@concordia.ellerman.id.au>
2016-07-19 3:59 ` Herbert Xu
2016-07-19 9:13 ` Michael Ellerman
2016-07-19 9:13 ` Michael Ellerman
[not found] ` <87poqa9eiz.fsf@@concordia.ellerman.id.au>
2016-07-19 9:52 ` Herbert Xu [this message]
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=20160719095239.GA24167@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=alastair@au1.ibm.com \
--cc=alastair@d-silva.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--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