From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Alex Dubov <oakad@yahoo.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] MEMSTICK: Add driver for Ricoh R5C592 Card reader.
Date: Fri, 06 Aug 2010 04:27:26 +0300 [thread overview]
Message-ID: <1281058046.3513.2.camel@maxim-laptop> (raw)
In-Reply-To: <1281057246.19943.20.camel@Joe-Laptop.home>
On Thu, 2010-08-05 at 18:14 -0700, Joe Perches wrote:
> On Thu, 2010-08-05 at 17:25 +0300, Maxim Levitsky wrote:
> > Signed-off-by: Maxim Levitsky <maximlevitsky@gmail.com>
>
> Trivial comments:
>
> > ---
> > MAINTAINERS | 6 +
> > +RICOH R5C592 MEMORYSTICK DRIVER
> > +M: Maxim Levitsky <maximlevitsky@gmail.com>
> > +S: Maintained
> > +F: drivers/memstick/host/r592.c
> > +F: drivers/memstick/host/r592.h
>
> Patterns in maintainers can use wildcards
Didn't know about that, thanks!
>
> F: drivers/memstick/host/r592*
>
> > --- /dev/null
> > +++ b/drivers/memstick/host/r592.c
> > @@ -0,0 +1,889 @@
> []
> > +static char *tpc_names[] = {
>
> const ?
Sure
>
> > + "MS_TPC_READ_MG_STATUS",
> > + "MS_TPC_READ_LONG_DATA",
>
> []
>
> > +#define dbg(format, ...) \
> > + if (debug) \
> > + printk(KERN_DEBUG DRV_NAME ": " format "\n", ## __VA_ARGS__)
> > +
> > +#define dbg_verbose(format, ...) \
> > + if (debug > 1) \
> > + printk(KERN_DEBUG DRV_NAME ": " format "\n", ## __VA_ARGS__)
> > +
> > +#define dbg_reg(format, ...) \
> > + if (debug > 2) \
> > + printk(KERN_DEBUG DRV_NAME ": " format "\n", ## __VA_ARGS__)
> > +
>
> These style macros should use do { if (test) print(); } while (9)
> so they could be used without problems in if/else blocks.
>
> Maybe it'd be better to have and use 1 macro with a level passed:
>
> #define dbg(level, format, ...) \
> do { \
> if (debug > level) \
> printk(KERN_DEBUG pr_fmt(format), ##__VA_ARGS__); \
> } while (0)
Thinking again about that, why not...
>
> > +#define message(format, ...) \
> > + printk(KERN_INFO DRV_NAME ": " format "\n", ## __VA_ARGS__)
>
> Why not just use pr_info?
Will look at that.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2010-08-06 1:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 14:25 [PATCH 0/2 V2 resend] Driver for Ricoh cardreader + few fixes Maxim Levitsky
2010-08-05 14:25 ` [PATCH 1/3] memstick: init sysfs attributes Maxim Levitsky
2010-08-05 14:25 ` [PATCH 2/3] MEMSTICK: fix hangs on unexpected device removal in mspro_blk Maxim Levitsky
2010-08-05 14:25 ` [PATCH 3/3] MEMSTICK: Add driver for Ricoh R5C592 Card reader Maxim Levitsky
2010-08-06 1:14 ` Joe Perches
2010-08-06 1:27 ` Maxim Levitsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-05 15:23 [PATCH 0/2 V3] Driver for Ricoh cardreader + few fixes Maxim Levitsky
2010-08-05 15:23 ` [PATCH 3/3] MEMSTICK: Add driver for Ricoh R5C592 Card reader Maxim Levitsky
2010-08-30 10:48 [PATCH 0/3 RESEND] My work on MemoryStick system Maxim Levitsky
2010-08-30 10:48 ` [PATCH 3/3] MEMSTICK: Add driver for Ricoh R5C592 Card reader Maxim Levitsky
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=1281058046.3513.2.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oakad@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox