Skip to contentSkip to conversation

yet more file moves

RFC Dominik Brodowski 3 participants 4 messages Aug 27, 2003

lore
Share & tools
lore
#0 lore 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

#1 lore raw
Quoted 4 lines · Dominik Brodowski

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/

Sounds OK. But the arch-specific stuff in 2.6 is in arch/i386/kernel/cpu/cpufreq if I remember correctly?

Bas.

#2 lore raw
Quoted 6 lines · Bas Mevissen
Quoted 4 lines · Dominik Brodowski

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/

Dominik: I agreed for b), especially for acpi.c if we want it in 2.4. (BTW, I may commit soon a new version for it, have you done some stuff related to that one?)

Quoted 2 lines

Sounds OK. But the arch-specific stuff in 2.6 is in arch/i386/kernel/cpu/cpufreq if I remember correctly?

Bas: Correct, but cvs is rude sometimes, and patchin.sh does the Right Thing(c)(tm).

Signature · 4 lines
Ducrot Bruno

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.
#3 lore raw
Quoted 11 lines · Ducrot Bruno
Quoted 6 lines · Bas Mevissen
Quoted 4 lines · Dominik Brodowski

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/

Dominik: I agreed for b), especially for acpi.c if we want it in 2.4. (BTW, I may commit soon a new version for it, have you done some stuff related to that one?)

oh yes, I have - but only in my head, but not on my harddisk... So if you have done something wrt acpi already, commit it; I'll post my changes for comments and/or inclusion when they're ready. Might take a week or two, though.

Dominik