Linux Power Management development
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Joe Perches <joe@perches.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Kevin Hilman <khilman@kernel.org>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-omap@vger.kernel.org
Subject: Re: [PATCH 3/3] cpufreq: Use consistent prefixing via pr_fmt
Date: Wed, 6 Apr 2016 11:53:15 +0530	[thread overview]
Message-ID: <20160406062315.GU20655@vireshk-i7> (raw)
In-Reply-To: <45c8dae5844fb626ab6f4e59298e225c3315269e.1459887986.git.joe@perches.com>

On 05-04-16, 13:28, Joe Perches wrote:
> Use the more common kernel style adding a define for pr_fmt.
> 
> Miscellanea:
> 
> o Remove now unused PFX defines
> 
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
>  drivers/cpufreq/acpi-cpufreq.c            |  8 ++---
>  drivers/cpufreq/cpufreq-nforce2.c         | 20 +++++------
>  drivers/cpufreq/e_powersaver.c            | 38 ++++++++++----------
>  drivers/cpufreq/elanfreq.c                |  2 ++
>  drivers/cpufreq/ia64-acpi-cpufreq.c       |  5 +--
>  drivers/cpufreq/longhaul.c                | 60 +++++++++++++++----------------
>  drivers/cpufreq/loongson2_cpufreq.c       |  7 ++--
>  drivers/cpufreq/maple-cpufreq.c           |  6 ++--
>  drivers/cpufreq/omap-cpufreq.c            |  5 ++-
>  drivers/cpufreq/p4-clockmod.c             | 10 +++---
>  drivers/cpufreq/pmac32-cpufreq.c          |  8 +++--
>  drivers/cpufreq/pmac64-cpufreq.c          | 28 ++++++++-------
>  drivers/cpufreq/powernow-k6.c             | 15 ++++----
>  drivers/cpufreq/powernow-k7.c             | 43 +++++++++++-----------
>  drivers/cpufreq/pxa2xx-cpufreq.c          | 13 +++----
>  drivers/cpufreq/s3c2412-cpufreq.c         | 14 ++++----
>  drivers/cpufreq/s3c2440-cpufreq.c         |  2 ++
>  drivers/cpufreq/s3c24xx-cpufreq-debugfs.c |  2 ++
>  drivers/cpufreq/s3c24xx-cpufreq.c         |  8 +++--
>  drivers/cpufreq/s5pv210-cpufreq.c         |  6 ++--
>  drivers/cpufreq/sc520_freq.c              |  6 ++--
>  drivers/cpufreq/speedstep-centrino.c      |  5 +--
>  drivers/cpufreq/speedstep-ich.c           |  8 +++--
>  drivers/cpufreq/speedstep-lib.c           |  4 ++-
>  drivers/cpufreq/speedstep-smi.c           |  4 ++-
>  25 files changed, 181 insertions(+), 146 deletions(-)

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

-- 
viresh

  reply	other threads:[~2016-04-06  6:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 20:28 [PATCH 0/3] cpufreq: logging consistency changes Joe Perches
2016-04-05 20:28 ` [PATCH 1/3] intel_pstate: Use pr_fmt Joe Perches
2016-04-05 21:43   ` Srinivas Pandruvada
2016-04-06 14:51     ` Doug Smythies
2016-04-06 15:01       ` Viresh Kumar
2016-04-06 15:12       ` Joe Perches
2016-04-06 15:47         ` Doug Smythies
2016-04-06  6:14   ` Viresh Kumar
2016-04-05 20:28 ` [PATCH 2/3] cpufreq: Convert printk(KERN_<LEVEL> to pr_<level> Joe Perches
2016-04-06  6:20   ` Viresh Kumar
2016-04-05 20:28 ` [PATCH 3/3] cpufreq: Use consistent prefixing via pr_fmt Joe Perches
2016-04-06  6:23   ` Viresh Kumar [this message]
2016-04-22  0:40 ` [PATCH 0/3] cpufreq: logging consistency changes 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=20160406062315.GU20655@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=joe@perches.com \
    --cc=khilman@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --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