linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: linux-kernel@vger.kernel.org
Cc: Russell King <linux@arm.linux.org.uk>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org
Subject: [PATCH 0/2] drivers/input/serio: Use pr_fmt and pr_<level>
Date: Wed, 27 Oct 2010 10:19:09 -0700	[thread overview]
Message-ID: <cover.1288198838.git.joe@perches.com> (raw)

Standardize the logging messages a bit.

Joe Perches (2):
  drivers/input/serio/i8042: Use pr_<level>, pr_fmt. Fix dbg and __FILE__ use
  drivers/input/serio: Use pr_fmt and pr_<level>

 drivers/input/serio/ambakmi.c         |    5 ++-
 drivers/input/serio/ct82c710.c        |   10 ++--
 drivers/input/serio/gscps2.c          |   15 +++---
 drivers/input/serio/hil_mlc.c         |   17 +++---
 drivers/input/serio/hp_sdc.c          |   51 +++++++++---------
 drivers/input/serio/hp_sdc_mlc.c      |   46 ++++++++--------
 drivers/input/serio/i8042-x86ia64io.h |    2 +-
 drivers/input/serio/i8042.c           |   94 +++++++++++++++-----------------
 drivers/input/serio/i8042.h           |   19 ++++---
 drivers/input/serio/maceps2.c         |    5 ++-
 drivers/input/serio/parkbd.c          |    8 ++-
 drivers/input/serio/q40kbd.c          |    6 ++-
 drivers/input/serio/rpckbd.c          |    6 ++-
 drivers/input/serio/sa1111ps2.c       |   11 +++--
 drivers/input/serio/serio.c           |    8 ++--
 drivers/input/serio/serio_raw.c       |    8 ++-
 drivers/input/serio/serport.c         |    6 ++-
 17 files changed, 167 insertions(+), 150 deletions(-)

-- 
1.7.3.1.g432b3.dirty


             reply	other threads:[~2010-10-27 17:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 17:19 Joe Perches [this message]
2010-10-27 17:19 ` [PATCH 1/2] drivers/input/serio/i8042: Use pr_<level>, pr_fmt. Fix dbg and __FILE__ use Joe Perches
2010-10-27 17:19 ` [PATCH 2/2] drivers/input/serio: Use pr_fmt and pr_<level> Joe Perches

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.1288198838.git.joe@perches.com \
    --to=joe@perches.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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).