linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: linux-pm@vger.kernel.org, linux-omap@vger.kernel.org
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Len Brown <lenb@kernel.org>, Kevin Hilman <khilman@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] cpufreq: logging consistency changes
Date: Tue,  5 Apr 2016 13:28:22 -0700	[thread overview]
Message-ID: <cover.1459887986.git.joe@perches.com> (raw)

Trivial consistency changes.

Joe Perches (3):
  intel_pstate: Use pr_fmt
  cpufreq: Convert printk(KERN_<LEVEL> to pr_<level>
  cpufreq: Use consistent prefixing via pr_fmt

 drivers/cpufreq/acpi-cpufreq.c            | 16 +++---
 drivers/cpufreq/cpufreq-nforce2.c         | 28 +++++------
 drivers/cpufreq/e_powersaver.c            | 62 ++++++++++-------------
 drivers/cpufreq/elanfreq.c                |  4 +-
 drivers/cpufreq/ia64-acpi-cpufreq.c       | 10 ++--
 drivers/cpufreq/intel_pstate.c            | 18 ++++---
 drivers/cpufreq/longhaul.c                | 84 +++++++++++++------------------
 drivers/cpufreq/loongson2_cpufreq.c       |  7 ++-
 drivers/cpufreq/maple-cpufreq.c           | 11 ++--
 drivers/cpufreq/omap-cpufreq.c            |  7 ++-
 drivers/cpufreq/p4-clockmod.c             | 19 ++-----
 drivers/cpufreq/pmac32-cpufreq.c          | 14 +++---
 drivers/cpufreq/pmac64-cpufreq.c          | 47 +++++++++--------
 drivers/cpufreq/powernow-k6.c             | 16 +++---
 drivers/cpufreq/powernow-k7.c             | 70 +++++++++++---------------
 drivers/cpufreq/pxa2xx-cpufreq.c          | 18 +++----
 drivers/cpufreq/s3c2412-cpufreq.c         | 15 +++---
 drivers/cpufreq/s3c2440-cpufreq.c         |  6 ++-
 drivers/cpufreq/s3c24xx-cpufreq-debugfs.c |  4 +-
 drivers/cpufreq/s3c24xx-cpufreq.c         | 59 +++++++++++-----------
 drivers/cpufreq/s5pv210-cpufreq.c         | 10 ++--
 drivers/cpufreq/sc520_freq.c              | 10 ++--
 drivers/cpufreq/speedstep-centrino.c      |  6 +--
 drivers/cpufreq/speedstep-ich.c           |  8 +--
 drivers/cpufreq/speedstep-lib.c           | 11 ++--
 drivers/cpufreq/speedstep-smi.c           |  7 +--
 26 files changed, 269 insertions(+), 298 deletions(-)

-- 
2.8.0.rc4.16.g56331f8


             reply	other threads:[~2016-04-05 20:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 20:28 Joe Perches [this message]
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
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=cover.1459887986.git.joe@perches.com \
    --to=joe@perches.com \
    --cc=khilman@kernel.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=srinivas.pandruvada@linux.intel.com \
    --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).