[lkml]   [2003]   [Mar]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH][RFC] Re: cpufreq: allow user to specify voltage

> Here's my suggestion, (partly) based on something Patrick Mochel suggested
> for the passing of attribute files of cpufreq drivers to the cpufreq core:
> a NULL-terminated list of device_attributes *attr is passed to the core. And
> if attr itself is NULL, no attribute is passed, of course. Using this
> approach, this patch against cpufreq-CVS-HEAD adds a file
> /sys/devices/sys/cpu0/scaling_available_freqs (something Carl Thompson
> asked for)

Strange, I need

> @@ -166,8 +166,11 @@
> /* optional, for the moment */
> int (*init) (struct cpufreq_policy *policy);
> int (*exit) (struct cpufreq_policy *policy);
> + struct device_attribute *attr[];

to change this to *attr[99] if I want it to compile...

When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:33    [W:0.030 / U:0.500 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site