From: clabbe.montjoie@gmail.com (Corentin LABBE)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 0/2] crypto: sunxi-ss: fix 64-bit compilation
Date: Sat, 16 Jan 2016 21:32:45 +0100 [thread overview]
Message-ID: <569AA8ED.7050404@gmail.com> (raw)
In-Reply-To: <1452252249-12040-1-git-send-email-andre.przywara@arm.com>
Le 08/01/2016 12:24, Andre Przywara a ?crit :
> (resending to add linux-crypto, patches unchanged)
>
> Hi,
>
> these two patches provide a different approach to an issue I tried
> to fix lately [1].
> Instead of casting everything I now promote local types to size_t, so
> that the min3() arguments naturally match in type.
> As size_t is defined as "unsigned int" on 32-bit architectures
> anyway, that actually does not change anything there, but instead
> provides a clean approach to get it compiled for arm64.
>
> I split this up because 1/2 seems much cleaner to me than 2/2, so we
> can have a separate discussion/merge process on this.
>
> Cheers,
> Andre.
>
> [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-December/395689.html
>
> Andre Przywara (2):
> crypto: sunxi-ss-cipher: promote variables to match types in min3()
> calls
> crypto: sunxi-ss-hash: promote variables to match types in min3()
> calls
>
> drivers/crypto/sunxi-ss/sun4i-ss-cipher.c | 20 ++++++++++----------
> drivers/crypto/sunxi-ss/sun4i-ss-hash.c | 12 ++++++------
> drivers/crypto/sunxi-ss/sun4i-ss.h | 2 +-
> 3 files changed, 17 insertions(+), 17 deletions(-)
>
Hello
Sorry for this late answer.
I am in trouble with those patch, so we have with Andre a long conversation about it.
Basically, sun4i-ss will never be available on 64bits platform. (A64 will have a totally new crypto engine).
So letting it to compile under 64bit arch is only useful when goal is to add COMPILE_TEST for it.
But COMPILE_TEST cannot simply be added with those patch since some arches (x86/x86_64 at least) does not have writesl/readsl available.
The conclusion is that it is simpler to block 64bit build for sun4i-ss.
Regards
LABBE Corentin
next prev parent reply other threads:[~2016-01-16 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 11:24 [RESEND PATCH 0/2] crypto: sunxi-ss: fix 64-bit compilation Andre Przywara
2016-01-08 11:24 ` [RESEND PATCH 1/2] crypto: sunxi-ss-cipher: promote variables to match types in min3() calls Andre Przywara
2016-01-08 11:24 ` [RESEND PATCH 2/2] crypto: sunxi-ss-hash: " Andre Przywara
2016-01-16 20:32 ` Corentin LABBE [this message]
2016-01-18 10:01 ` [RESEND PATCH 0/2] crypto: sunxi-ss: fix 64-bit compilation Andre Przywara
2016-01-18 10:15 ` Borislav Petkov
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=569AA8ED.7050404@gmail.com \
--to=clabbe.montjoie@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).