From: Andre Przywara <andre.przywara@arm.com>
To: Corentin Labbe <clabbe.montjoie@gmail.com>,
maxime.ripard@free-electrons.com, Chen-Yu Tsai <wens@csie.org>,
arnd@arndb.de
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
linux-sunxi@googlegroups.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] crypto: sunxi-ss: fix 64-bit compilation
Date: Thu, 7 Jan 2016 15:58:16 +0000 [thread overview]
Message-ID: <1452182298-4653-1-git-send-email-andre.przywara@arm.com> (raw)
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(-)
--
2.6.4
next reply other threads:[~2016-01-07 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 15:58 Andre Przywara [this message]
2016-01-07 15:58 ` [PATCH 1/2] crypto: sunxi-ss-cipher: promote variables to match types in min3() calls Andre Przywara
2016-01-07 15:58 ` [PATCH 2/2] crypto: sunxi-ss-hash: " Andre Przywara
2016-01-08 9:59 ` [PATCH 0/2] crypto: sunxi-ss: fix 64-bit compilation Herbert Xu
2016-01-08 11:15 ` Andre Przywara
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=1452182298-4653-1-git-send-email-andre.przywara@arm.com \
--to=andre.przywara@arm.com \
--cc=arnd@arndb.de \
--cc=clabbe.montjoie@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=maxime.ripard@free-electrons.com \
--cc=wens@csie.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
all inboxes | Powered by JetHome®