From: Dominik Brodowski <linux@brodo.de>
To: cpufreq@www.linux.org.uk
Subject: [RFC] yet more file moves
Date: Wed, 27 Aug 2003 08:02:29 +0200 [thread overview]
Message-ID: <20030827060229.GA4315@brodo.de> (raw)
I hereby suggest that
a) for 2.4. and 2.6. drivers/cpufreq/userspace.c is moved to
drivers/cpufreq/cpufreq-userspace.c,
b) for 2.4, the x86 cpufreq drivers are moved to arch/i386/kernel/cpufreq/
Rationale:
to a) "userspace" as module name is too generic for the use of a small
subsystem like cpufreq.
to b) arch/i386/kernel/ is already very crowded. Let's not fill it
further, but move stuff to a seperate subdirectury, just like in 2.6.
Comments?
Dominik
next reply other threads:[~2003-08-27 6:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 6:02 Dominik Brodowski [this message]
2003-08-27 9:09 ` [RFC] yet more file moves Bas Mevissen
2003-08-27 11:02 ` Ducrot Bruno
2003-08-27 12:41 ` 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=20030827060229.GA4315@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