Re: linux-next: manual merge of the tip tree with the crypto-current tree

From	Stephen Rothwell <sfr@canb.auug.org.au>
Newsgroups	linux.kernel
Subject	Re: linux-next: manual merge of the tip tree with the crypto-current tree
Date	2015-10-09 04:10 +0200
Message-ID	<qhvi9-4YJ-3@gated-at.bofh.it> (permalink)
References	<qhuYO-4mT-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Hi all,

On Fri, 9 Oct 2015 12:47:00 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> diff --cc arch/x86/crypto/camellia_aesni_avx_glue.c
> index bacaa13acac5,12e729bfe71b..000000000000
> --- a/arch/x86/crypto/camellia_aesni_avx_glue.c
> +++ b/arch/x86/crypto/camellia_aesni_avx_glue.c
> @@@ -554,12 -554,8 +554,14 @@@ static int __init camellia_aesni_init(v
>   {
>   	const char *feature_name;
>   
>  +	if (!cpu_has_avx || !cpu_has_aes || !cpu_has_osxsave) {
>  +		pr_info("AVX or AES-NI instructions are not detected.\n");
>  +		return -ENODEV;
>  +	}
>  +
>  +	if (!cpu_has_xfeatures(XSTATE_SSE | XSTATE_YMM, &feature_name)) {

OOPS, I clearly meant to remove that line as well (which I have now done).

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

linux-next: manual merge of the tip tree with the crypto-current  tree Stephen Rothwell <sfr@canb.auug.org.au> - 2015-10-09 03:50 +0200
  Re: linux-next: manual merge of the tip tree with the  crypto-current tree Ben Hutchings <ben@decadent.org.uk> - 2015-10-09 04:00 +0200
  Re: linux-next: manual merge of the tip tree with the  crypto-current tree Stephen Rothwell <sfr@canb.auug.org.au> - 2015-10-09 04:10 +0200

csiph-web