From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Herbert Xu <herbert@gondor•apana.org.au>
Cc: linux-next@vger•kernel.org,
Sebastian Andrzej Siewior <sebastian@breakpoint•cc>
Subject: linux-next: crypto tree build failure
Date: Wed, 22 Apr 2009 14:47:06 +1000 [thread overview]
Message-ID: <20090422144706.2d540852.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]
Hi Herbert,
Today's linux-next build (powerpc allyesconfig) failed like this:
drivers/crypto/padlock-aes.c:21:22: error: asm/i387.h: No such file or directory
drivers/crypto/padlock-aes.c: In function 'aes_encrypt':
drivers/crypto/padlock-aes.c:251: error: implicit declaration of function 'irq_ts_save'
drivers/crypto/padlock-aes.c:253: error: implicit declaration of function 'irq_ts_restore'
drivers/crypto/padlock-aes.c: In function 'padlock_init':
drivers/crypto/padlock-aes.c:458: error: 'cpu_has_xcrypt' undeclared (first use in this function)
drivers/crypto/padlock-aes.c:463: error: 'cpu_has_xcrypt_enabled' undeclared (first use in this function)
drivers/crypto/padlock-sha.c:25:22: error: asm/i387.h: No such file or directory
drivers/crypto/padlock-sha.c: In function 'padlock_do_sha1':
drivers/crypto/padlock-sha.c:115: error: implicit declaration of function 'irq_ts_save'
drivers/crypto/padlock-sha.c:119: error: implicit declaration of function 'irq_ts_restore'
drivers/crypto/padlock-sha.c: In function 'padlock_init':
drivers/crypto/padlock-sha.c:265: error: 'cpu_has_phe' undeclared (first use in this function)
drivers/crypto/padlock-sha.c:270: error: 'cpu_has_phe_enabled' undeclared (first use in this function)
Caused by commit 93628c83b00492fc592a29d0dc91efb1d55c6e24 ("crypto:
padlock - Enable on x86_64") which actually enabled it for everything
(except UML)!
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-04-22 4:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 4:47 Stephen Rothwell [this message]
2009-04-22 5:00 ` linux-next: crypto tree build failure Herbert Xu
2009-04-22 7:06 ` Stephen Rothwell
2009-04-22 7:36 ` Sebastian Andrzej Siewior
-- strict thread matches above, loose matches on Subject: below --
2009-01-20 2:30 Stephen Rothwell
2009-01-20 3:04 ` Huang Ying
2009-01-20 4:57 ` Herbert Xu
2009-01-20 5:21 ` Herbert Xu
2009-01-20 5:44 ` Stephen Rothwell
2008-12-04 2:43 Stephen Rothwell
2008-12-04 6:38 ` Herbert Xu
2008-11-11 4:07 Stephen Rothwell
2008-11-11 4:22 ` Herbert Xu
2008-11-11 5:34 ` Stephen Rothwell
2008-08-05 4:02 Stephen Rothwell
2008-08-05 5:36 ` Herbert Xu
2008-08-05 13:33 ` Stephen Rothwell
2008-08-05 14:05 ` Herbert Xu
2008-08-05 14:20 ` Stephen Rothwell
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=20090422144706.2d540852.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sebastian@breakpoint$(echo .)cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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