From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: linux-next: build failure after merge of the crypto-current tree Date: Thu, 10 Nov 2011 16:50:19 +0100 Message-ID: <20111110155019.GA7068@elte.hu> References: <20111101115851.2e37ac680db78bdba0661691@canb.auug.org.au> <20111102200900.GA3454@hades> <20111102233936.GA10058@gondor.apana.org.au> <20111103055824.GC22141@secunet.com> <20111103061628.GA12678@gondor.apana.org.au> <20111103101554.GA17569@onza.mythic-beasts.com> <20111103114214.GA14681@gondor.apana.org.au> <20111103115933.GA12708@onza.mythic-beasts.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mx2.mail.elte.hu ([157.181.151.9]:44543 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753561Ab1KJPwO (ORCPT ); Thu, 10 Nov 2011 10:52:14 -0500 Content-Disposition: inline In-Reply-To: <20111103115933.GA12708@onza.mythic-beasts.com> Sender: linux-next-owner@vger.kernel.org List-ID: To: Luis Henriques Cc: Herbert Xu , Steffen Klassert , Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org * Luis Henriques 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935257Ab1KJPwQ (ORCPT ); Thu, 10 Nov 2011 10:52:16 -0500 Received: from mx2.mail.elte.hu ([157.181.151.9]:44543 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753561Ab1KJPwO (ORCPT ); Thu, 10 Nov 2011 10:52:14 -0500 X-Greylist: delayed 6800 seconds by postgrey-1.27 at vger.kernel.org; Thu, 10 Nov 2011 10:52:14 EST Date: Thu, 10 Nov 2011 16:50:19 +0100 From: Ingo Molnar To: Luis Henriques Cc: Herbert Xu , Steffen Klassert , Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: linux-next: build failure after merge of the crypto-current tree Message-ID: <20111110155019.GA7068@elte.hu> References: <20111101115851.2e37ac680db78bdba0661691@canb.auug.org.au> <20111102200900.GA3454@hades> <20111102233936.GA10058@gondor.apana.org.au> <20111103055824.GC22141@secunet.com> <20111103061628.GA12678@gondor.apana.org.au> <20111103101554.GA17569@onza.mythic-beasts.com> <20111103114214.GA14681@gondor.apana.org.au> <20111103115933.GA12708@onza.mythic-beasts.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111103115933.GA12708@onza.mythic-beasts.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=AWL,BAYES_00 autolearn=no SpamAssassin version=3.3.1 -2.0 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 0.0 AWL AWL: From: address is in the auto white-list Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Luis Henriques 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