From: Randy Dunlap <randy.dunlap@oracle.com>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-crypto@vger.kernel.org, Andy Whitcroft <apw@shadowen.org>
Subject: Re: [BUILD_FAILURE] linux-next: Tree for May 19 - build fails on cryptd_alloc_hash ()
Date: Mon, 19 May 2008 10:26:27 -0700 [thread overview]
Message-ID: <20080519102627.997d61ef.randy.dunlap@oracle.com> (raw)
In-Reply-To: <4831B3F6.5080101@linux.vnet.ibm.com>
On Mon, 19 May 2008 22:38:06 +0530 Kamalesh Babulal wrote:
> Hi,
>
> The next-20080519 kernel build fails on the x86_64 machine, when compiled
> with the randconfig.
>
> LD .tmp_vmlinux1
> crypto/built-in.o: In function `cryptd_alloc_hash':
> /root/kernels/linux-2.6.26-rc3/crypto/cryptd.c:485: undefined reference to `crypto_ahash_type'
> make: *** [.tmp_vmlinux1] Error 1
Fixed on Thu May 15: http://lkml.org/lkml/2008/5/15/433
and Herbert says that he merged it on Fri May 16,
so why did it miss being in linux-next on Mon May 19?
Wrong tree/branch/whatever?
---
~Randy
next prev parent reply other threads:[~2008-05-19 17:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 7:41 linux-next: Tree for May 19 Stephen Rothwell
2008-05-19 10:27 ` [BUG] linux-next: Tree for May 19 - BUG at arch/x86/kernel/io_apic_64.c:353! Kamalesh Babulal
2008-05-21 17:26 ` [BUG] linux-next: Tree for May 19/20/21 " Kamalesh Babulal
2008-05-22 0:15 ` Stephen Rothwell
2008-05-22 10:22 ` Kamalesh Babulal
2008-05-19 17:08 ` [BUILD_FAILURE] linux-next: Tree for May 19 - build fails on cryptd_alloc_hash () Kamalesh Babulal
2008-05-19 17:26 ` Randy Dunlap [this message]
2008-05-20 6:40 ` Herbert Xu
2008-05-19 18:42 ` linux-next: Tree for May 19 Thomas Meyer
2008-05-20 4:19 ` 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=20080519102627.997d61ef.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=apw@shadowen.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).