mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Woody Suwalski <terraluna977@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: 3.8-rc[12] cpufreq build errors...
Date: Sat, 05 Jan 2013 22:53:35 +0100	[thread overview]
Message-ID: <2446683.GzoeULsVfp@vostro.rjw.lan> (raw)
In-Reply-To: <50E83B2D.9000609@gmail.com>

On Saturday, January 05, 2013 09:39:41 AM Woody Suwalski wrote:
> Rafael, in 3.8 kernel part of the common logic has been moved to a 
> separate cpufreq_governor.c file.
> According to the Makefile, the cpufreq_governor.o is to be linked to 
> other cpufreq  modules.
> 
> However I see that a separate malformed cpufreq_governor.ko is created, 
> and then the real modules can not work without the common logic either.
> 
> The build config is a simple 32-bit config, on top of vanilla source.
> 
> I submit a verbose build log with "ls *.ko" and some "modinfo" outputs 
> attached to the bottom.
> Clearly the build subsystem is misinterpreting the build intentions.
> 
> Could you please check if you see the same issue in your builds?
> I am using a 32-bit October-ish Debian Testing as a build machine (Eeepc 
> netbook).

This issue has already been reported and there's a fix scheduled for
inclusion in the master branch of the linux-pm.git tree.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  reply	other threads:[~2013-01-05 21:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-05 14:39 Woody Suwalski
2013-01-05 21:53 ` Rafael J. Wysocki [this message]
2013-01-05 20:12 Larry Finger
2013-01-05 22:19 ` Woody Suwalski

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=2446683.GzoeULsVfp@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=terraluna977@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®