From: Dominik Brodowski <linux@brodo.de>
To: cpufreq@www.linux.org.uk
Subject: move kernel/cpufreq.c to drivers/cpufreq/cpufreq.c?
Date: Mon, 14 Jul 2003 18:55:51 +0200 [thread overview]
Message-ID: <20030714165551.GA1925@brodo.de> (raw)
Back in the early days the whole cpufreq core was located in one file --
kernel/cpufreq.c. Now, there are several cross-architecture files for
cpufreq present in drivers/cpufreq. Because of this, I'd favor moving
kernel/cpufreq.c to drivers/cpufreq/cpufreq.c.
Also, cpufreq.c could be split up into "notifiers.c" and "cpufreq.c" --
cpufreq.c can be "modularized" then. It only needs to be "y" on ARM_SA11?0
and if CONFIG_ACPI_PROCESSOR="y" is (on x86). Is there interest in a patch
for this, too?
Dominik
reply other threads:[~2003-07-14 16:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030714165551.GA1925@brodo.de \
--to=linux@brodo.de \
--cc=cpufreq@www.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox