From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932790AbcBCC31 (ORCPT ); Tue, 2 Feb 2016 21:29:27 -0500 Received: from mail-pf0-f176.google.com ([209.85.192.176]:32951 "EHLO mail-pf0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932448AbcBCC3X (ORCPT ); Tue, 2 Feb 2016 21:29:23 -0500 Date: Wed, 3 Feb 2016 07:59:20 +0530 From: Viresh Kumar To: "Rafael J. Wysocki" Cc: Rafael Wysocki , Juri Lelli , Lists linaro-kernel , "linux-pm@vger.kernel.org" , Saravana Kannan , Peter Zijlstra , Michael Turquette , Steve Muckle , Vincent Guittot , Morten Rasmussen , dietmar.eggemann@arm.com, Linux Kernel Mailing List Subject: Re: [PATCH 1/5] cpufreq: governor: Kill declare_show_sampling_rate_min() Message-ID: <20160203022920.GN31828@vireshk> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02-02-16, 21:23, Rafael J. Wysocki wrote: > To me, this is not about the macro, but about moving min_sampling_rate > to governor tunables, so my subject would be something like "cpufreq: > governor: Treat min_sampling_rate as a governor-specific tunable". > > My changelog, then, would be something like the following: > > "The min_sampling_rate governor tunable is a field in struct dbs_data, > so it has to be handled in a special way separate from the rest of > governor tunables. In particular, that requires a special macro to be > present for creating its show/store sysfs attribute callbacks. > > However, there is no real need for the data structures and code in > question to be arranged this way and if min_sampling_rate is moved to > data structures holding the other governor tunables, the sysfs > attribute creation macros that work with those tunables will also work > with min_sampling_rate and the special macro for it won't be necessary > any more. That will make it easier to modify the governor code going > forward, so do it." I just copy pasted it with: [ Rafael: Written changelog ] just before my sign-off. Thanks. -- viresh