linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Markus Mayer <code@mmayer.net>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Power Management List <linux-pm@vger.kernel.org>,
	Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Markus Mayer <mmayer@broadcom.com>
Subject: Re: [PATCH v3] cpufreq: stats: clear statistics
Date: Tue, 8 Nov 2016 09:39:40 +0530	[thread overview]
Message-ID: <20161108040940.GJ21030@vireshk-i7> (raw)
In-Reply-To: <20161107180223.44536-1-code@mmayer.net>

On 07-11-16, 10:02, Markus Mayer wrote:
> From: Markus Mayer <mmayer@broadcom.com>
> 
> Allow CPUfreq statistics to be cleared by writing anything to
> /sys/.../cpufreq/stats/reset.
> 
> Signed-off-by: Markus Mayer <mmayer@broadcom.com>
> ---
> 
> Changes since v2:
>     - changed name of write-only macro to cpufreq_freq_attr_wo()
>     - removed "perm" parameter from write-only macro
>     - squashed the two separate commits into a single one
> 
> Changes since v1:
>     - add new cpufreq_freq_attr_wr_perm() macro for write-only
>       attributes (because this is a separate commit, this patch has
>       turned into a series)
>     - remove the Kconfig option, compiling the code unconditionally
>     - remove show_reset()
>     - cpufreq_stats_clear_table() takes a struct cpufreq_stats * as
>       argument rather than a struct cpufreq_policy *
> 
>  Documentation/cpu-freq/cpufreq-stats.txt |  6 ++++++
>  drivers/cpufreq/cpufreq_stats.c          | 22 ++++++++++++++++++++++
>  include/linux/cpufreq.h                  |  4 ++++
>  3 files changed, 32 insertions(+)

Acked-by: Viresh Kumar <viresh.kumar@linaro.org>

-- 
viresh

  reply	other threads:[~2016-11-08  4:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-07 18:02 [PATCH v3] cpufreq: stats: clear statistics Markus Mayer
2016-11-08  4:09 ` Viresh Kumar [this message]
2016-11-14  0:31   ` Rafael J. Wysocki

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=20161108040940.GJ21030@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=code@mmayer.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mmayer@broadcom.com \
    --cc=rjw@rjwysocki.net \
    /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).