mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Dominik Brodowski <linux@brodo.de>
Cc: davej@suse.de, John Clemens <john@deater.net>,
	cpufreq@www.linux.org.uk,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] Re: cpufreq: allow user to specify voltage
Date: Thu, 6 Mar 2003 01:29:46 +0100	[thread overview]
Message-ID: <20030306002945.GA31895@elf.ucw.cz> (raw)
In-Reply-To: <20030228211638.GA888@brodo.de>

Hi!

> 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...
								Pavel

-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

  reply	other threads:[~2003-03-06  0:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 22:55 Pavel Machek
2003-02-25  0:41 ` Dominik Brodowski
2003-02-25 18:03   ` Pavel Machek
2003-02-25 18:24     ` Dominik Brodowski
2003-02-25 19:09       ` Pavel Machek
2003-02-25 19:28         ` John Clemens
2003-02-25 19:33           ` Pavel Machek
2003-02-28 21:16             ` [PATCH][RFC] " Dominik Brodowski
2003-03-06  0:29               ` Pavel Machek [this message]
2003-03-06  0:36               ` Pavel Machek
2003-03-06 20:42               ` Pavel Machek

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=20030306002945.GA31895@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=cpufreq@www.linux.org.uk \
    --cc=davej@suse.de \
    --cc=john@deater.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@brodo.de \
    /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

all inboxes | Powered by JetHome®