From: Herbert Xu <herbert@gondor.apana.org.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jeff Garzik <jeff@garzik.org>,
Raveendra Padasalagi <raveendra.padasalagi@broadcom.com>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: sha3 - Add missing ULL suffixes for 64-bit constants
Date: Tue, 9 Aug 2016 00:06:28 +0800 [thread overview]
Message-ID: <20160808160628.GA32116@gondor.apana.org.au> (raw)
In-Reply-To: <1470245823-21090-1-git-send-email-geert@linux-m68k.org>
On Wed, Aug 03, 2016 at 07:37:03PM +0200, Geert Uytterhoeven wrote:
> On 32-bit (e.g. with m68k-linux-gnu-gcc-4.1):
>
> crypto/sha3_generic.c:27: warning: integer constant is too large for ‘long’ type
> crypto/sha3_generic.c:28: warning: integer constant is too large for ‘long’ type
> crypto/sha3_generic.c:29: warning: integer constant is too large for ‘long’ type
> crypto/sha3_generic.c:29: warning: integer constant is too large for ‘long’ type
> crypto/sha3_generic.c:31: warning: integer constant is too large for ‘long’ type
> crypto/sha3_generic.c:31: warning: integer constant is too large for ‘long’ type
> crypto/sha3_generic.c:32: warning: integer constant is too large for ‘long’ type
> crypto/sha3_generic.c:32: warning: integer constant is too large for ‘long’ type
> crypto/sha3_generic.c:32: warning: integer constant is too large for ‘long’ type
> crypto/sha3_generic.c:33: warning: integer constant is too large for ‘long’ type
> crypto/sha3_generic.c:33: warning: integer constant is too large for ‘long’ type
> crypto/sha3_generic.c:34: warning: integer constant is too large for ‘long’ type
> crypto/sha3_generic.c:34: warning: integer constant is too large for ‘long’ type
>
> Fixes: 53964b9ee63b7075 ("crypto: sha3 - Add SHA-3 hash algorithm")
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
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
prev parent reply other threads:[~2016-08-08 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 17:37 Geert Uytterhoeven
2016-08-08 16:06 ` Herbert Xu [this message]
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=20160808160628.GA32116@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=jeff@garzik.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raveendra.padasalagi@broadcom.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
all inboxes | Powered by JetHome®