From: Jan Glauber <jang@linux.vnet.ibm.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Martin Schwidefksy <schwidefsky@de.ibm.com>
Subject: Re: crypto: sha-s390 - Switch to shash
Date: Tue, 03 Feb 2009 15:16:22 +0000 [thread overview]
Message-ID: <1233674182.1536.28.camel@localhost.localdomain> (raw)
In-Reply-To: <20090203014806.GA32506@gondor.apana.org.au>
On Tue, 2009-02-03 at 12:48 +1100, Herbert Xu wrote:
> On Mon, Feb 02, 2009 at 06:01:07PM +0000, Jan Glauber wrote:
> >
> > The patch is not yet in cryptodev, so I applied it on top of cryptodev.
> > Compiling it gives me the following error:
> >
> > CC [M] arch/s390/crypto/sha256_s390.o
> > arch/s390/crypto/sha_common.c: In function ‘s390_sha_update’:
> > arch/s390/crypto/sha_common.c:23: error: implicit declaration of function ‘crypto_shash_blocksize’
> > make[1]: *** [arch/s390/crypto/sha_common.o] Error 1
>
> Thanks for testing! It turns out that this was the first in-tree
> user for crypto_shash_blocksize so I'll need to add it.
With this little typo-patch shash works fine on s390.
Cheers, Jan
--- ./arch/s390/crypto/sha256_s390.c.shash 2009-02-03 13:43:47.000000000
+0100
+++ ./arch/s390/crypto/sha256_s390.c 2009-02-03 13:43:53.000000000 +0100
@@ -26,7 +26,7 @@
static int sha256_init(struct shash_desc *desc)
{
- struct s390_sha_ctx *sctx = shash_desc_ctx(tfm);
+ struct s390_sha_ctx *sctx = shash_desc_ctx(desc);
sctx->state[0] = SHA256_H0;
sctx->state[1] = SHA256_H1;
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-02-03 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 22:55 crypto: sha-s390 - Switch to shash Herbert Xu
2009-01-28 3:56 ` Herbert Xu
2009-02-02 12:20 ` Martin Schwidefsky
2009-02-02 18:01 ` Jan Glauber
2009-02-03 1:48 ` Herbert Xu
2009-02-03 15:16 ` Jan Glauber [this message]
2009-02-04 0:05 ` 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=1233674182.1536.28.camel@localhost.localdomain \
--to=jang@linux.vnet.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.