public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Luis Henriques <henrix@camandro•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Herbert Xu <herbert@gondor•apana.org.au>,
	Steffen Klassert <steffen.klassert@secunet•com>
Subject: Re: linux-next: build failure after merge of the crypto-current tree
Date: Wed, 2 Nov 2011 20:09:13 +0000	[thread overview]
Message-ID: <20111102200900.GA3454@hades> (raw)
In-Reply-To: <20111101115851.2e37ac680db78bdba0661691@canb.auug.org.au>

Hi,

In gmane.linux.kernel, you wrote:
> --Signature=_Tue__1_Nov_2011_11_58_51_+1100_R__G+wW+4zIqxa7J
> Content-Type: text/plain; charset=US-ASCII
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> Hi Herbert,
>
> After merging the crypto-current tree, today's linux-next build (x86_64
> allmodconfig) failed like this:

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.

Cheers,
--
Luis Henriques

next prev parent reply	other threads:[~2011-11-02 20:53 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 [this message]
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
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=20111102200900.GA3454@hades \
    --to=henrix@camandro$(echo .)org \
    --cc=herbert@gondor$(echo .)apana.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=steffen.klassert@secunet$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox