Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 5 Mar 2003 19:20:15 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 5 Mar 2003 19:20:15 -0500 Received: from [195.39.17.254] ([195.39.17.254]:9476 "EHLO Elf.ucw.cz") by vger.kernel.org with ESMTP id ; Wed, 5 Mar 2003 19:20:13 -0500 Date: Thu, 6 Mar 2003 01:29:46 +0100 From: Pavel Machek To: Dominik Brodowski Cc: davej@suse.de, John Clemens , cpufreq@www.linux.org.uk, kernel list Subject: Re: [PATCH][RFC] Re: cpufreq: allow user to specify voltage Message-ID: <20030306002945.GA31895@elf.ucw.cz> References: <20030225190949.GM12028@atrey.karlin.mff.cuni.cz> <20030225193341.GA19556@atrey.karlin.mff.cuni.cz> <20030228211638.GA888@brodo.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030228211638.GA888@brodo.de> X-Warning: Reading this can be dangerous to your mental health. User-Agent: Mutt/1.5.3i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1083 Lines: 30 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?] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/