All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Thomas Renninger <trenn@suse.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: cpufreq tree build failure
Date: Mon, 3 Aug 2009 19:44:00 -0400	[thread overview]
Message-ID: <20090803234400.GA16934@redhat.com> (raw)
In-Reply-To: <200908040122.15733.trenn@suse.de>

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

  reply	other threads:[~2009-08-03 23:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03  2:28 linux-next: cpufreq tree build failure Stephen Rothwell
2009-08-03 23:22 ` Thomas Renninger
2009-08-03 23:44   ` Dave Jones [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-24  6:21 Stephen Rothwell
2009-02-24 16:51 ` Dave Jones
2009-02-25  3:29   ` Stephen Rothwell
2009-02-25  3:45     ` Dave Jones
2009-02-25  4:23       ` Stephen Rothwell
2009-02-05  7:54 Stephen Rothwell
2009-02-05  9:33 ` Thomas Renninger
2009-02-05  9:47 ` Thomas Renninger
2009-02-05 17:45   ` Dave Jones
2009-02-05 20:57     ` Thomas Renninger
2009-02-05 21:34       ` Dave Jones
2009-01-20  2:50 Stephen Rothwell
2009-01-20  5:30 ` Dave Jones
2009-01-20  6:23   ` Stephen Rothwell

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=20090803234400.GA16934@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=trenn@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.