linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: tianyu.lan@intel.com
Cc: lenb@kernel.org, cpufreq@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] ACPI/Cpureq: Using cpufreq_freq_attr_rw macro to define CPB(Core Performance Boost) attribute
Date: Tue, 13 Aug 2013 13:38:16 +0200	[thread overview]
Message-ID: <3406040.uy3dFkLbfM@vostro.rjw.lan> (raw)
In-Reply-To: <1376359553-5671-1-git-send-email-tianyu.lan@intel.com>

On Tuesday, August 13, 2013 10:05:53 AM tianyu.lan@intel.com wrote:
> From: Lan Tianyu <tianyu.lan@intel.com>
> 
> Standardise the defintion of attribute cpb in the acpi-cpufreq driver
> via cpufreq_freq_attr_rw macro.
> 
> Signed-off-by: Lan Tianyu <tianyu.lan@intel.com>

Queued up for 3.12.

Thanks,
Rafael


> ---
>  drivers/cpufreq/acpi-cpufreq.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/cpufreq/acpi-cpufreq.c b/drivers/cpufreq/acpi-cpufreq.c
> index e673670..414ee4d 100644
> --- a/drivers/cpufreq/acpi-cpufreq.c
> +++ b/drivers/cpufreq/acpi-cpufreq.c
> @@ -197,7 +197,7 @@ static ssize_t show_cpb(struct cpufreq_policy *policy, char *buf)
>  	return sprintf(buf, "%u\n", boost_enabled);
>  }
>  
> -static struct freq_attr cpb = __ATTR(cpb, 0644, show_cpb, store_cpb);
> +cpufreq_freq_attr_rw(cpb);
>  #endif
>  
>  static int check_est_cpu(unsigned int cpuid)
> 
-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

      reply	other threads:[~2013-08-13 11:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13  2:05 [PATCH] ACPI/Cpureq: Using cpufreq_freq_attr_rw macro to define CPB(Core Performance Boost) attribute tianyu.lan
2013-08-13 11:38 ` Rafael J. Wysocki [this message]

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=3406040.uy3dFkLbfM@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=cpufreq@vger.kernel.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=tianyu.lan@intel.com \
    /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).