public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Woody Suwalski <terraluna977@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3.8-rc[12] cpufreq build errors...
Date: Sat, 05 Jan 2013 14:12:46 -0600	[thread overview]
Message-ID: <50E8893E.8090502@lwfinger.net> (raw)

Woody,

There is a patch pending that fixes this problem. See
http://lkml.indiana.edu/hypermail/linux/kernel/1212.3/01201.html. Note that 
Rafael wrote "If you don't mind, I'll rename CONFIG_CPU_FREQ_GOVERNOR to
CONFIG_CPU_FREQ_GOV_COMMON when applying it, though". I think this patch is 
working its way through the system, but I have not seem it in mainline yet.

Larry

             reply	other threads:[~2013-01-05 20:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-05 20:12 Larry Finger [this message]
2013-01-05 22:19 ` 3.8-rc[12] cpufreq build errors Woody Suwalski
  -- strict thread matches above, loose matches on Subject: below --
2013-01-05 14:39 Woody Suwalski
2013-01-05 21:53 ` Rafael J. Wysocki

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=50E8893E.8090502@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=linux-kernel@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