From: Dave Jones <davej@redhat.com>
To: bert hubert <bert.hubert@netherlabs.nl>,
Alexey Starikovskiy <alexey_y_starikovskiy@linux.intel.com>,
linux-kernel@vger.kernel.org, zwane@arm.linux.org.uk,
venkatesh.pallipadi@intel.com, tony@atomide.com, akpm@osdl.org,
cpufreq@lists.linux.org.uk, len.brown@intel.com
Subject: Re: 2.6.17 -> 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
Date: Mon, 31 Jul 2006 16:38:29 -0400 [thread overview]
Message-ID: <20060731203829.GF4631@redhat.com> (raw)
In-Reply-To: <20060731185713.GA16797@outpost.ds9a.nl>
On Mon, Jul 31, 2006 at 08:57:13PM +0200, bert hubert wrote:
> On Mon, Jul 31, 2006 at 12:20:46PM -0400, Dave Jones wrote:
>
> > Your change in your previous mail makes sense to me though,
> > so I'll commit it to cpufreq.git later today.
>
> Do you think this will make 2.6.18? Otherwise any kernel with acpi_list
> compiled in will have no frequency scaling, unless it supports scaling over
> ACPI.
Yes, I'll queue it for .18
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-07-31 20:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 12:08 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4 bert hubert
2006-07-30 16:07 ` Tomasz Torcz
2006-07-30 16:51 ` 2.6.17 -> " bert hubert
2006-07-30 18:07 ` Alexey Starikovskiy
2006-07-30 18:44 ` bert hubert
2006-07-30 18:44 ` bert hubert
2006-07-30 19:01 ` Dave Jones
2006-07-30 19:19 ` bert hubert
2006-07-31 7:08 ` bert hubert
2006-07-31 16:20 ` Dave Jones
2006-07-31 18:57 ` bert hubert
2006-07-31 20:38 ` Dave Jones [this message]
2006-07-30 17:45 ` Zwane Mwaikambo
2006-07-31 5:56 ` Tomasz Torcz
2006-07-31 14:04 ` Zwane Mwaikambo
2006-07-31 15:22 ` Tomasz Torcz
2006-07-30 19:46 ` Arjan van de Ven
2006-07-30 19:53 ` bert hubert
2006-07-31 7:50 ` David Rees
2006-07-31 8:12 ` bert hubert
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=20060731203829.GF4631@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=alexey_y_starikovskiy@linux.intel.com \
--cc=bert.hubert@netherlabs.nl \
--cc=cpufreq@lists.linux.org.uk \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.com \
--cc=venkatesh.pallipadi@intel.com \
--cc=zwane@arm.linux.org.uk \
/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.