linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Valentin <edubezval@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
	linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
	l.majewski@samsung.com
Subject: Re: [PATCH 1/7] cpufreq: Fix formatting issues in 'struct cpufreq_driver'
Date: Wed, 26 Nov 2014 13:57:36 -0400	[thread overview]
Message-ID: <20141126175734.GC1826@developer> (raw)
In-Reply-To: <3d727922615731d6e839f1ce5cb977bd3fc6ed24.1416980447.git.viresh.kumar@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 4318 bytes --]

On Wed, Nov 26, 2014 at 11:22:56AM +0530, Viresh Kumar wrote:
> Adding any new callback to 'struct cpufreq_driver' gives following checkpatch
> warning:
> 
> WARNING: Unnecessary space before function pointer arguments
> +	void	(*usable)	(struct cpufreq_policy *policy);
> 
> This is because we have been using a tab spacing between function pointer name
> and its arguments and the new one tried to follow that.
> 
> Though we normally don't try to fix every checkpatch warning, specially around
> formatting issues as that creates unnecessary noise over lists. But I thought we
> better fix this so that new additions don't generate these warnings plus it
> looks far better/symmetric now.
> 
> So, remove these tab spacing issues in 'struct cpufreq_driver' only + fix
> alignment of all members.
> 
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>

Reviewed-by: Eduardo Valentin <edubezval@gmail.com>
Tested-by: Eduardo Valentin <edubezval@gmail.com>

> ---
>  include/linux/cpufreq.h | 50 ++++++++++++++++++++++++-------------------------
>  1 file changed, 25 insertions(+), 25 deletions(-)
> 
> diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
> index 503b085..db3c130 100644
> --- a/include/linux/cpufreq.h
> +++ b/include/linux/cpufreq.h
> @@ -217,26 +217,26 @@ __ATTR(_name, 0644, show_##_name, store_##_name)
>  
>  
>  struct cpufreq_driver {
> -	char			name[CPUFREQ_NAME_LEN];
> -	u8			flags;
> -	void			*driver_data;
> +	char		name[CPUFREQ_NAME_LEN];
> +	u8		flags;
> +	void		*driver_data;
>  
>  	/* needed by all drivers */
> -	int	(*init)		(struct cpufreq_policy *policy);
> -	int	(*verify)	(struct cpufreq_policy *policy);
> +	int		(*init)(struct cpufreq_policy *policy);
> +	int		(*verify)(struct cpufreq_policy *policy);
>  
>  	/* define one out of two */
> -	int	(*setpolicy)	(struct cpufreq_policy *policy);
> +	int		(*setpolicy)(struct cpufreq_policy *policy);
>  
>  	/*
>  	 * On failure, should always restore frequency to policy->restore_freq
>  	 * (i.e. old freq).
>  	 */
> -	int	(*target)	(struct cpufreq_policy *policy,	/* Deprecated */
> -				 unsigned int target_freq,
> -				 unsigned int relation);
> -	int	(*target_index)	(struct cpufreq_policy *policy,
> -				 unsigned int index);
> +	int		(*target)(struct cpufreq_policy *policy,
> +				  unsigned int target_freq,
> +				  unsigned int relation);	/* Deprecated */
> +	int		(*target_index)(struct cpufreq_policy *policy,
> +					unsigned int index);
>  	/*
>  	 * Only for drivers with target_index() and CPUFREQ_ASYNC_NOTIFICATION
>  	 * unset.
> @@ -252,27 +252,27 @@ struct cpufreq_driver {
>  	 * wish to switch to intermediate frequency for some target frequency.
>  	 * In that case core will directly call ->target_index().
>  	 */
> -	unsigned int (*get_intermediate)(struct cpufreq_policy *policy,
> -					 unsigned int index);
> -	int	(*target_intermediate)(struct cpufreq_policy *policy,
> -				       unsigned int index);
> +	unsigned int	(*get_intermediate)(struct cpufreq_policy *policy,
> +					    unsigned int index);
> +	int		(*target_intermediate)(struct cpufreq_policy *policy,
> +					       unsigned int index);
>  
>  	/* should be defined, if possible */
> -	unsigned int	(*get)	(unsigned int cpu);
> +	unsigned int	(*get)(unsigned int cpu);
>  
>  	/* optional */
> -	int	(*bios_limit)	(int cpu, unsigned int *limit);
> +	int		(*bios_limit)(int cpu, unsigned int *limit);
>  
> -	int	(*exit)		(struct cpufreq_policy *policy);
> -	void	(*stop_cpu)	(struct cpufreq_policy *policy);
> -	int	(*suspend)	(struct cpufreq_policy *policy);
> -	int	(*resume)	(struct cpufreq_policy *policy);
> -	struct freq_attr	**attr;
> +	int		(*exit)(struct cpufreq_policy *policy);
> +	void		(*stop_cpu)(struct cpufreq_policy *policy);
> +	int		(*suspend)(struct cpufreq_policy *policy);
> +	int		(*resume)(struct cpufreq_policy *policy);
> +	struct freq_attr **attr;
>  
>  	/* platform specific boost support code */
> -	bool                    boost_supported;
> -	bool                    boost_enabled;
> -	int     (*set_boost)    (int state);
> +	bool		boost_supported;
> +	bool		boost_enabled;
> +	int		(*set_boost)(int state);
>  };
>  
>  /* flags */
> -- 
> 2.0.3.693.g996b0fd
> 

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-11-26 17:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26  5:52 [PATCH 0/7] cpufreq: Register cooling device after policy is usable Viresh Kumar
2014-11-26  5:52 ` [PATCH 1/7] cpufreq: Fix formatting issues in 'struct cpufreq_driver' Viresh Kumar
2014-11-26 17:57   ` Eduardo Valentin [this message]
2014-11-26  5:52 ` [PATCH 2/7] cpufreq-dt: pass 'policy->related_cpus' to of_cpufreq_cooling_register() Viresh Kumar
2014-11-26 17:55   ` Eduardo Valentin
2014-11-26  5:52 ` [PATCH 3/7] cpufreq: Introduce ->usable() callback for cpufreq drivers Viresh Kumar
2014-11-26 17:58   ` Eduardo Valentin
2014-11-27  0:25   ` Rafael J. Wysocki
2014-11-27  0:28     ` Viresh Kumar
2014-11-26  5:52 ` [PATCH 4/7] cpufreq-dt: register cooling device from ->usable() callback Viresh Kumar
2014-11-26 17:59   ` Eduardo Valentin
2014-11-26  5:53 ` [PATCH 5/7] cpu_cooling: Don't match min/max frequencies for all CPUs on cooling register Viresh Kumar
2014-11-27 15:35   ` Eduardo Valentin
2014-11-28  9:19     ` Viresh Kumar
2014-11-26  5:53 ` [PATCH 6/7] cpu_cooling: don't iterate over all allowed_cpus to update cpufreq policy Viresh Kumar
2014-11-26  5:53 ` [PATCH 7/7] cpu_cooling: Don't check is_cpufreq_valid() Viresh Kumar
2014-11-26 17:54 ` [PATCH 0/7] cpufreq: Register cooling device after policy is usable Eduardo Valentin
2014-11-27  0:26   ` Rafael J. Wysocki
2014-11-27 15:33   ` Eduardo Valentin
2014-11-28  6:27     ` Viresh Kumar
2014-11-26 18:01 ` Eduardo Valentin

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=20141126175734.GC1826@developer \
    --to=edubezval@gmail.com \
    --cc=l.majewski@samsung.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=viresh.kumar@linaro.org \
    /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;
as well as URLs for NNTP newsgroup(s).