From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Gortmaker Subject: Re: linux-next: build failure after merge of the moduleh tree Date: Sun, 31 Jul 2011 02:59:54 -0400 Message-ID: <20110731065954.GF31842@windriver.com> References: <20110729170933.b7bfc24dcf48201928bd5890@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Return-path: Received: from mail.windriver.com ([147.11.1.11]:53877 "EHLO mail.windriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751185Ab1GaG77 (ORCPT ); Sun, 31 Jul 2011 02:59:59 -0400 Content-Disposition: inline In-Reply-To: <20110729170933.b7bfc24dcf48201928bd5890@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, "David S. Miller" [linux-next: build failure after merge of the moduleh tree] On 29/07/2011 (Fri 17:09) Stephen Rothwell wrote: > Hi Paul, > > After merging the moduleh tree, today's linux-next build (sparc defconfig) > failed like this: [...] > Again, I have left these unfixed in linux-next today. Thanks, I've got these sparc32 items all fixed up; I wasn't thinking that my allyesconfig would have excluded sparc32. I've retested with the two defconfigs, all[yes,no,mod]config to make sure I didn't miss any other module.h cleanup fallout for sparc. Paul. > -- > Cheers, > Stephen Rothwell sfr@canb.auug.org.au > http://www.canb.auug.org.au/~sfr/