From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Jan Glauber <jang@linux.vnet.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-next@vger.kernel.org
Subject: linux-next / s390 crypto breakage
Date: Wed, 2 Sep 2009 13:35:26 +0200 [thread overview]
Message-ID: <20090902113526.GC4754@osiris.boeblingen.de.ibm.com> (raw)
Hi Herbert,
your patch "crypto: shash - Export/import hash state only" causes this
on s390:
CC arch/s390/crypto/sha1_s390.o
arch/s390/crypto/sha1_s390.c: In function 'sha1_import':
arch/s390/crypto/sha1_s390.c:63: warning: initialization from incompatible pointer type
arch/s390/crypto/sha1_s390.c: At top level:
arch/s390/crypto/sha1_s390.c:78: warning: initialization from incompatible pointer type
CC arch/s390/crypto/sha_common.o
CC arch/s390/crypto/sha256_s390.o
arch/s390/crypto/sha256_s390.c: In function 'sha256_import':
arch/s390/crypto/sha256_s390.c:59: warning: initialization from incompatible pointer type
arch/s390/crypto/sha256_s390.c: At top level:
arch/s390/crypto/sha256_s390.c:74: warning: initialization from incompatible pointer type
CC arch/s390/crypto/sha512_s390.o
arch/s390/crypto/sha512_s390.c: In function 'sha512_import':
arch/s390/crypto/sha512_s390.c:58: warning: initialization from incompatible pointer type
arch/s390/crypto/sha512_s390.c: At top level:
arch/s390/crypto/sha512_s390.c:76: warning: initialization from incompatible pointer type
arch/s390/crypto/sha512_s390.c:115: warning: initialization from incompatible pointer type
Looks like you missed some conversions. Could you (or Jan?) fix this please?
Thanks!
next reply other threads:[~2009-09-02 11:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 11:35 Heiko Carstens [this message]
2009-09-02 17:57 ` linux-next / s390 crypto breakage Jan Glauber
2009-09-02 22:04 ` Herbert Xu
2009-09-03 15:52 ` Jan Glauber
2009-09-05 6:28 ` 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=20090902113526.GC4754@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=jang@linux.vnet.ibm.com \
--cc=linux-next@vger.kernel.org \
--cc=schwidefsky@de.ibm.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;
as well as URLs for NNTP newsgroup(s).