From: Ingo Molnar <mingo@elte.hu>
To: Luis Henriques <henrix@camandro.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Steffen Klassert <steffen.klassert@secunet.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the crypto-current tree
Date: Thu, 10 Nov 2011 16:50:19 +0100 [thread overview]
Message-ID: <20111110155019.GA7068@elte.hu> (raw)
In-Reply-To: <20111103115933.GA12708@onza.mythic-beasts.com>
* Luis Henriques <henrix@camandro.org> wrote:
> On Thu, Nov 03, 2011 at 10:42:14PM +1100, Herbert Xu wrote:
> > On Thu, Nov 03, 2011 at 10:15:54AM +0000, Luis Henriques wrote:
> > >
> > > No, this did not solved the problem; build still fails. The problem is
> > > that, in lib/nlattr.c, we have:
> >
> > Ugh, for the time being I guess we'll have to wrap these within
> > CONFIG_NET, as I'd rather not have CONFIG_CRYPTO depend on CONFIG_NET.
> >
> > Please let me know whether this patch fixes the problem.
>
> Yep, it compiles and boots. Thanks for the patch.
v3.2-rc1 has been released with this (commonly triggering) build bug
included. Herbert, is the fix on the way to upstream?
Thanks,
Ingo
next prev parent reply other threads:[~2011-11-10 15:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 0:58 linux-next: build failure after merge of the crypto-current tree Stephen Rothwell
2011-11-01 1:11 ` Herbert Xu
2011-11-01 4:23 ` Stephen Rothwell
2011-11-01 5:18 ` Herbert Xu
2011-11-01 6:02 ` Stephen Rothwell
2011-11-02 20:09 ` Luis Henriques
2011-11-02 23:39 ` Herbert Xu
2011-11-03 5:58 ` Steffen Klassert
2011-11-03 6:16 ` Herbert Xu
2011-11-03 10:15 ` Luis Henriques
2011-11-03 11:42 ` Herbert Xu
2011-11-03 11:59 ` Luis Henriques
2011-11-10 15:50 ` Ingo Molnar [this message]
2011-11-10 22:50 ` 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=20111110155019.GA7068@elte.hu \
--to=mingo@elte.hu \
--cc=henrix@camandro.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=steffen.klassert@secunet.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).