From: "H. Peter Anvin" <hpa@zytor.com>
To: Tim Chen <tim.c.chen@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH v1] crypto: aesni - fix build on x86 (32bit)
Date: Mon, 06 Jan 2014 09:45:32 -0800 [thread overview]
Message-ID: <637fa237-687f-4e88-88d2-4a9dd0c2bf14@email.android.com> (raw)
In-Reply-To: <1389030119.2624.19.camel@schen9-DESK>
Can the code be adjusted to compile for 32 bit x86 or is that pointless?
Tim Chen <tim.c.chen@linux.intel.com> wrote:
>
>
>On Mon, 2013-12-30 at 15:52 +0200, Andy Shevchenko wrote:
>> It seems commit d764593a "crypto: aesni - AVX and AVX2 version of
>AESNI-GCM
>> encode and decode" breaks a build on x86_32 since it's designed only
>for
>> x86_64. This patch makes a compilation unit conditional to
>CONFIG_64BIT and
>> functions usage to CONFIG_X86_64.
>
>Thanks for catching and fixing it.
>
>Tim
>>
>> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
--
Sent from my mobile phone. Please pardon brevity and lack of formatting.
next prev parent reply other threads:[~2014-01-06 17:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 13:52 [PATCH v1] crypto: aesni - fix build on x86 (32bit) Andy Shevchenko
2013-12-31 11:57 ` Herbert Xu
2014-01-06 17:41 ` Tim Chen
2014-01-06 17:45 ` H. Peter Anvin [this message]
2014-01-06 17:57 ` Tim Chen
2014-01-06 18:00 ` H. Peter Anvin
2014-01-06 18:10 ` Tim Chen
2014-01-06 20:26 ` Borislav Petkov
2014-01-06 21:21 ` H. Peter Anvin
2014-01-06 23:39 ` Tim Chen
2014-01-06 23:41 ` H. Peter Anvin
2014-01-07 1:30 ` Herbert Xu
2014-01-09 9:03 ` Herbert Xu
2014-01-09 16:57 ` Tim Chen
2014-01-15 3:43 ` 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=637fa237-687f-4e88-88d2-4a9dd0c2bf14@email.android.com \
--to=hpa@zytor.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bp@alien8.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=tim.c.chen@linux.intel.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