From: Joe Perches <joe@perches.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input <linux-input@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.37? ] drivers/input: Use pr_<level>
Date: Wed, 04 Aug 2010 00:33:42 -0700 [thread overview]
Message-ID: <1280907222.1005.63.camel@Joe-Laptop.home> (raw)
In-Reply-To: <20100804043256.GB25256@core.coreip.homeip.net>
On Tue, 2010-08-03 at 21:32 -0700, Dmitry Torokhov wrote:
> Hi Joe,
Hi Dmitry.
> On Tue, Aug 03, 2010 at 11:40:50AM -0700, Joe Perches wrote:
> > Remove prefixes from printks and convert to pr_fmt/pr_<level>.
> Thanks for doing this, however instead of using pr_xxx() I'd like
> drivers that are integrated in driver model (serio, usb, gameport, etc,
> i.e. when we have 'struct device' available, exept for psmouse) to use
> drv_xxx() instead.
These files?
$ grep -rPl --include=*.[ch] "\bstruct\s+device\b" drivers/input | \
xargs grep -wl pr_fmt
drivers/input/keyboard/omap-keypad.c
drivers/input/mousedev.c
drivers/input/serio/serio.c
drivers/input/serio/i8042.c
drivers/input/evdev.c
drivers/input/joydev.c
drivers/input/gameport/gameport.c
drivers/input/touchscreen/htcpen.c
drivers/input/input-polldev.c
drivers/input/input.c
drivers/input/tablet/aiptek.c
drivers/input/misc/winbond-cir.c
drivers/input/misc/yealink.c
drivers/input/misc/ati_remote2.c
drivers/input/misc/wistron_btns.c
drivers/input/misc/ati_remote.c
drivers/input/mouse/psmouse-base.c
> That would make synaptics messages to come as "psmouse", right?
Yes.
> I think we should use
> #define pr_fmt(fmt) "synaptics: " fmt
> here and in the rest of specialized PS/2 protocol handlers.
Perhaps convert to what elantech uses
#define pr_fmt(fmt) KBUILD_BASENAME ": " fmt
$ grep -l "define pr_fmt" drivers/input/mouse/*.[ch] | \
xargs grep -il "ps2"
drivers/input/mouse/alps.c
drivers/input/mouse/elantech.c
drivers/input/mouse/lifebook.c
drivers/input/mouse/logips2pp.c
drivers/input/mouse/psmouse-base.c
drivers/input/mouse/sentelic.c
drivers/input/mouse/synaptics.c
drivers/input/mouse/trackpoint.c
Which ones do you want converted?
Any others?
next prev parent reply other threads:[~2010-08-04 7:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 18:40 Joe Perches
2010-08-04 4:32 ` Dmitry Torokhov
2010-08-04 7:33 ` Joe Perches [this message]
2010-08-04 8:04 ` Dmitry Torokhov
2010-08-04 8:44 ` Joe Perches
2010-08-05 6:44 ` Dmitry Torokhov
2010-08-05 7:29 ` [PATCH 0/9] " Joe Perches
2010-08-05 7:29 ` [PATCH 1/9] drivers/input/gameport: Use pr_fmt and pr_<level> Joe Perches
2010-08-05 7:29 ` [PATCH 2/9] drivers/input/joystick: " Joe Perches
2010-08-05 7:29 ` [PATCH 3/9] drivers/input/keyboard: " Joe Perches
2010-08-05 7:29 ` [PATCH 4/9] drivers/input/misc: " Joe Perches
2010-08-05 7:29 ` [PATCH 5/9] drivers/input/mouse: " Joe Perches
2010-08-05 7:29 ` [PATCH 6/9] drivers/input/serio: " Joe Perches
2010-08-05 7:29 ` [PATCH 7/9] drivers/input/tablet: " Joe Perches
2010-08-05 7:29 ` [PATCH 8/9] drivers/input/touchscreen: " Joe Perches
2010-08-05 7:29 ` [PATCH 9/9] drivers/input: " 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=1280907222.1005.63.camel@Joe-Laptop.home \
--to=joe@perches.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®