From: Steffen Klassert <steffen.klassert@secunet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Luis Henriques <henrix@camandro.org>,
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, 3 Nov 2011 06:58:24 +0100 [thread overview]
Message-ID: <20111103055824.GC22141@secunet.com> (raw)
In-Reply-To: <20111102233936.GA10058@gondor.apana.org.au>
On Thu, Nov 03, 2011 at 10:39:36AM +1100, Herbert Xu wrote:
> On Wed, Nov 02, 2011 at 08:09:13PM +0000, Luis Henriques wrote:
> >
> > I'm not sure if this is related, but I am currently unable to build mainline
> > kernel when disabling CONFIG_NET. This seems to be due to the patch serie:
> >
> > http://news.gmane.org/gmane.linux.kernel.cryptoapi/cutoff=6228
> >
> > For instance, commit 6ad414fe710d4fd3a8c8c6c2ad8fefcfcc207968 adds a dependency
> > over function nla_put(), which is only defined when CONFIG_NET is enabled.
>
> Indeed, I missed the dependency in the report functions which
> is built even when CRYPTO_USER is turned off.
>
> Does this patch fix the problem for you?
>
Hm, did you forget to add the patch to the mail?
next prev parent reply other threads:[~2011-11-03 5:58 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 [this message]
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
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=20111103055824.GC22141@secunet.com \
--to=steffen.klassert@secunet.com \
--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 \
/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).