From: Joe Perches <joe@perches.com>
To: Paulius Zaleckas <paulius.zaleckas@gmail.com>
Cc: Elly Jones <ellyjones@google.com>,
netdev@vger.kernel.org, dbrownell@users.sourceforge.net,
mjg59@srcf.ucam.org, jglasgow@google.com, msb@google.com,
olofj@google.com
Subject: Re: [PATCH 1/2] drivers/net/usb/qcusbnet: Checkpatch cleanups
Date: Fri, 01 Oct 2010 06:41:59 -0700 [thread overview]
Message-ID: <1285940519.752.10.camel@Joe-Laptop> (raw)
In-Reply-To: <4CA5E185.3090902@gmail.com>
On Fri, 2010-10-01 at 16:26 +0300, Paulius Zaleckas wrote:
> On 09/29/2010 05:39 AM, Joe Perches wrote:
> > Whitespace and removal of KERNEL_VERSION tests
> > Neaten DBG macro
>
> Why not use dev_dbg istead of this ugly DBG macro?
Currently, like a lot of other macros
in the tree, it uses a runtime flag to
control output.
dev_dbg doesn't have that capability.
next prev parent reply other threads:[~2010-10-01 13:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 17:10 [PATCH] Add Qualcomm Gobi 2000 driver Elly Jones
2010-09-28 17:16 ` Ben Hutchings
2010-09-28 18:11 ` Joe Perches
2010-09-28 21:23 ` Dan Williams
2010-10-04 15:03 ` Elly Jones
2010-09-29 2:39 ` [PATCH 0/2] qcusbnet: Cleanups Joe Perches
2010-09-29 2:39 ` [PATCH 1/2] drivers/net/usb/qcusbnet: Checkpatch cleanups Joe Perches
2010-09-29 3:09 ` [PATCH 3] drivers/net/usb/qcusbnet: Spelling and extern int debug cleanups Joe Perches
2010-10-01 13:26 ` [PATCH 1/2] drivers/net/usb/qcusbnet: Checkpatch cleanups Paulius Zaleckas
2010-10-01 13:41 ` Joe Perches [this message]
2010-10-01 13:54 ` Paulius Zaleckas
2010-09-29 2:39 ` [PATCH 2/2] drivers/net/usb/qcusbnet/qmidevice: Remove printhex, use print_hex_dump Joe Perches
2010-10-01 0:33 ` [PATCH 0/2] qcusbnet: Cleanups David Miller
2010-10-01 0:45 ` Joe Perches
2010-10-01 14:42 ` Elly Jones
2010-10-01 15:56 ` Joe Perches
2010-10-01 18:29 ` David Brownell
2010-10-01 13:37 ` [PATCH] Add Qualcomm Gobi 2000 driver Paulius Zaleckas
2010-10-01 13:50 ` Matthew Garrett
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=1285940519.752.10.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=dbrownell@users.sourceforge.net \
--cc=ellyjones@google.com \
--cc=jglasgow@google.com \
--cc=mjg59@srcf.ucam.org \
--cc=msb@google.com \
--cc=netdev@vger.kernel.org \
--cc=olofj@google.com \
--cc=paulius.zaleckas@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.