From: Dave Jones <davej@codemonkey.org.uk>
To: Dominik Brodowski <linux@brodo.de>
Cc: torvalds@transmeta.com, davej@suse.de,
linux-kernel@vger.kernel.org, cpufreq@www.linux.org.uk
Subject: Re: [PATCH] cpufreq: move frequency table helpers to extra module
Date: Thu, 13 Feb 2003 09:39:51 +0000 [thread overview]
Message-ID: <20030213093951.GA22151@codemonkey.org.uk> (raw)
In-Reply-To: <20030213091131.GA8909@brodo.de>
On Thu, Feb 13, 2003 at 10:11:31AM +0100, Dominik Brodowski wrote:
> The CPU frequency table helpers can easily be modularized --
> especially as they are not needed on all architectures, or for
> all drivers.
As most of the x86 drivers have been converted now, it looks like
it'd make more sense to conditionalise this on architecture, and
move the remaining x86 drivers over to the helpers (longrun/longhaul).
It just strikes me as silly that we have a config option that when
disabled could end up showing no chip drivers when the conversion
is complete.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2003-02-13 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 9:11 [PATCH] cpufreq: move frequency table helpers to extra module Dominik Brodowski
2003-02-13 9:39 ` Dave Jones [this message]
2003-02-13 10:00 ` Dominik Brodowski
2003-02-13 10:17 ` Roman Zippel
2003-02-13 11:14 ` [PATCH UPDATED] " Dominik Brodowski
2003-02-15 20:53 ` Linus Torvalds
2003-02-15 22:57 ` [PATCH] cpufreq: fix compilation of ACPI if !CPU_FREQ [Was: Re: [PATCH UPDATED] cpufreq: move frequency table helpers to extra module] Dominik Brodowski
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=20030213093951.GA22151@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=torvalds@transmeta.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