From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Jones Subject: Re: linux-next: cpufreq tree build failure Date: Mon, 3 Aug 2009 19:44:00 -0400 Message-ID: <20090803234400.GA16934@redhat.com> References: <20090803122819.6b738cad.sfr@canb.auug.org.au> <200908040122.15733.trenn@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mx2.redhat.com ([66.187.237.31]:44709 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932357AbZHCXoJ (ORCPT ); Mon, 3 Aug 2009 19:44:09 -0400 Content-Disposition: inline In-Reply-To: <200908040122.15733.trenn@suse.de> Sender: linux-next-owner@vger.kernel.org List-ID: To: Thomas Renninger Cc: Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org On Tue, Aug 04, 2009 at 01:22:14AM +0200, Thomas Renninger wrote: > On Monday 03 August 2009 04:28:19 am Stephen Rothwell wrote: > > Hi Dave, > > > > Today's linux-next build (x86_64 allmodconfig) failed like this: > > > > ERROR: "cpufreq_global_kobject" [drivers/cpufreq/cpufreq_ondemand.ko] > > undefined! > > > > Caused by commit 35b104d88338e5eddb36c670fea4752f6c10c82f ("[CPUFREQ] > > ondemand - Use global sysfs dir for tuning settings"). Presumably > > cpufreq_global_kobject needs an EXPORT_SYMBOL. > > Yep, that's it. Below is a fix. > > Thanks a lot, I'll roll this in with the previous patch, so as not to introduce a bisect-regression, and rebase the tree. Will push something out soon. thanks. Dave