From: Dave Jones <davej@redhat.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-acpi@vger.kernel.org, cpufreq@lists.linux.org.uk,
Christian <christiand59@web.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [discuss] Linux 2.6.19-rc4: known unfixed regressions (v2)
Date: Mon, 6 Nov 2006 12:49:28 -0500 [thread overview]
Message-ID: <20061106174928.GB19283@redhat.com> (raw)
In-Reply-To: <20061106173528.GQ5778@stusta.de>
On Mon, Nov 06, 2006 at 06:35:28PM +0100, Adrian Bunk wrote:
> config X86_POWERNOW_K8
> tristate "AMD Opteron/Athlon64 PowerNow!"
> select CPU_FREQ_TABLE
> depends (ACPI_PROCESSOR || ACPI_PROCESSOR=n)
>
> But in the end, the best solution depends on how many percent of the
> X86_POWERNOW_K8 users have Christian's problem of requiring
> ACPI_PROCESSOR. If there are only very few people with this problem, I'd
> say leave it as it is.
Well, it's been this way for a while, and only recently this has come up.
There was a similar report for powernow-k7, which has a similar construct.
Dave
--
http://www.codemonkey.org.uk
prev parent reply other threads:[~2006-11-06 17:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0610302019560.25218@g5.osdl.org>
2006-10-31 19:56 ` 2.6.19-rc4: known unfixed regressions Adrian Bunk
2006-10-31 20:11 ` Greg KH
2006-10-31 20:12 ` Arjan van de Ven
2006-11-03 2:41 ` Linux 2.6.19-rc4: known unfixed regressions (v2) Adrian Bunk
2006-11-05 6:48 ` 2.6.19-rc4: known unfixed regressions (v3) Adrian Bunk
2006-11-05 9:30 ` Jeff Chua
2006-11-06 17:47 ` [discuss] " Andi Kleen
2006-11-07 2:17 ` Ernst Herzberg
2006-11-07 5:41 ` Len Brown
2006-11-07 20:05 ` Ernst Herzberg
[not found] ` <454AFD01.4080306@linux.intel.com>
[not found] ` <20061103155656.GA1000@redhat.com>
[not found] ` <200611051832.13285.christiand59@web.de>
[not found] ` <20061105200448.GE859@redhat.com>
2006-11-06 17:35 ` [discuss] Linux 2.6.19-rc4: known unfixed regressions (v2) Adrian Bunk
2006-11-06 17:49 ` Dave Jones [this message]
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=20061106174928.GB19283@redhat.com \
--to=davej@redhat.com \
--cc=bunk@stusta.de \
--cc=christiand59@web.de \
--cc=cpufreq@lists.linux.org.uk \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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