LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linux-crypto@vger.kernel.org, linuxppc-dev@ozlabs.org,
linux-kernel@vger.kernel.org, mhcerri@linux.vnet.ibm.com,
pfsmorigo@linux.vnet.ibm.com
Subject: Re: [PATCH 2/2] crypto: vmx - Remove overly verbose printk from AES XTS init
Date: Sat, 12 May 2018 00:19:26 +0800 [thread overview]
Message-ID: <20180511161926.bboeiec6fjjrg2rk@gondor.apana.org.au> (raw)
In-Reply-To: <20180503122930.17448-2-mpe@ellerman.id.au>
On Thu, May 03, 2018 at 10:29:30PM +1000, Michael Ellerman wrote:
> In p8_aes_xts_init() we do a printk(KERN_INFO ...) to report the
> fallback implementation we're using. However with a slow console this
> can significantly affect the speed of crypto operations. So remove it.
>
> Fixes: c07f5d3da643 ("crypto: vmx - Adding support for XTS")
> Cc: stable@vger.kernel.org # v4.8+
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> ---
> drivers/crypto/vmx/aes_xts.c | 2 --
> 1 file changed, 2 deletions(-)
Patch applied. 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
next prev parent reply other threads:[~2018-05-11 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 12:29 [PATCH 1/2] crypto: vmx - Remove overly verbose printk from AES init routines Michael Ellerman
2018-05-03 12:29 ` [PATCH 2/2] crypto: vmx - Remove overly verbose printk from AES XTS init Michael Ellerman
2018-05-11 16:19 ` Herbert Xu [this message]
2018-05-11 16:19 ` [PATCH 1/2] crypto: vmx - Remove overly verbose printk from AES init routines Herbert Xu
2018-05-14 11:18 ` 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=20180511161926.bboeiec6fjjrg2rk@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mhcerri@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=pfsmorigo@linux.vnet.ibm.com \
/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).