From: Joe Perches <joe@perches.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Paul Mundt <lethal@linux-sh.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] usb: Convert dbg to pr_eliminated and pr_debug
Date: Mon, 18 Jun 2012 09:39:10 -0700 [thread overview]
Message-ID: <1340037550.2182.27.camel@joe2Laptop> (raw)
In-Reply-To: <20120618161445.GA17155@kroah.com>
On Mon, 2012-06-18 at 09:14 -0700, Greg Kroah-Hartman wrote:
> On Mon, Jun 18, 2012 at 09:07:10AM -0700, Joe Perches wrote:
> > On Mon, 2012-06-18 at 08:23 -0700, Greg Kroah-Hartman wrote:
[]
> > > No, I really want to delete this macro entirely, and am slowly working
> > > toward that, moving drivers to use the correct dev_dbg() macro instead.
[]
> > And anyway, why go slowly? Why not just do it?
>
> I take it you didn't see the 200+ patches in 3.5-rc1 that did a lot of
> this work already? Is that slow?
You said slowly.
I don't care much one way or another but
scripts work pretty quickly, humans less so.
dbg is certainly an ugly little wart though.
next prev parent reply other threads:[~2012-06-18 16:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 2:25 [PATCH 0/5] printk: Add eliminated_printk Joe Perches
2012-06-18 2:25 ` [PATCH 1/5] printk: Add eliminated_printk macro Joe Perches
2012-06-18 2:25 ` [PATCH 2/5] printk: Convert pr_devel to use eliminated_printk Joe Perches
2012-06-18 2:25 ` [PATCH 3/5] usb: Convert dbg to pr_eliminated and pr_debug Joe Perches
2012-06-18 6:08 ` Paul Mundt
2012-06-18 15:23 ` Greg Kroah-Hartman
2012-06-18 16:07 ` Joe Perches
2012-06-18 16:14 ` Greg Kroah-Hartman
2012-06-18 16:39 ` Joe Perches [this message]
2012-06-18 2:25 ` [PATCH 4/5] fujitsu-laptop: Convert dbg_printk and vdbg_printk to fuj_dbg Joe Perches
2012-06-18 7:08 ` Jonathan Woithe
2012-06-18 2:25 ` [PATCH 5/5] thinkpad_acpi: Convert dbg_printk to tp_dbg and tp_vdbg Joe Perches
2012-06-24 0:40 ` Henrique de Moraes Holschuh
2012-06-24 3:06 ` Joe Perches
2012-06-24 14:42 ` Henrique de Moraes Holschuh
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=1340037550.2182.27.camel@joe2Laptop \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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