From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Herbert Xu <herbert@gondor•apana.org.au>
Cc: linux-next@vger•kernel.org, Adrian-Ken Rueegsegger <ken@codelabs•ch>
Subject: linux-next: crypto tree build failure
Date: Thu, 4 Dec 2008 13:43:31 +1100 [thread overview]
Message-ID: <20081204134331.016d38c4.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
Hi Herbert,
Today's linux-next build (x86_64 allmodconfig) failed like this:
crypto/built-in.o: In function `md5_mod_init':
crypto/md5.c:239: undefined reference to `crypto_register_shash'
crypto/built-in.o: In function `md5_mod_fini':
crypto/md5.c:244: undefined reference to `crypto_unregister_shash'
Presumably caused by commit 08cf233c1f29fc1cad8786b3c73647625810665b
("crypto: md5 - Switch to shash").
I have dropped the crypto tree 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:[~2008-12-04 2:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 2:43 Stephen Rothwell [this message]
2008-12-04 6:38 ` linux-next: crypto tree build failure Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2009-04-22 4:47 Stephen Rothwell
2009-04-22 5:00 ` Herbert Xu
2009-04-22 7:06 ` Stephen Rothwell
2009-04-22 7:36 ` Sebastian Andrzej Siewior
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-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=20081204134331.016d38c4.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=ken@codelabs$(echo .)ch \
--cc=linux-next@vger$(echo .)kernel.org \
/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