From: Greg KH <greg@kroah.com>
To: "Henri Häkkinen" <henuxd@gmail.com>
Cc: gregkh@suse.de, mithlesh@linsyssoft.com, wfp5p@virginia.edu,
reodge@gmail.com, andrea.gelmini@gelma.net,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging:comedi: Fixed coding convention issues.
Date: Thu, 17 Jun 2010 16:02:09 -0700 [thread overview]
Message-ID: <20100617230209.GA391@kroah.com> (raw)
In-Reply-To: <1276497255-2186-1-git-send-email-henuxd@gmail.com>
On Mon, Jun 14, 2010 at 09:34:15AM +0300, Henri Häkkinen wrote:
> Cleaned up and fixed coding convention issues as reporteed by
> checkpatch.pl tool on the file `drivers.c'. Added logging macros
> to `comedidev.h'. Replaced "BUG:" printk functions calls with
> BUG_ON macro.
>
> Signed-off-by: Henri Häkkinen <henuxd@gmail.com>
> ---
> drivers/staging/comedi/comedidev.h | 54 +++++++++++++++-
> drivers/staging/comedi/drivers.c | 118 +++++++++++++++--------------------
> 2 files changed, 102 insertions(+), 70 deletions(-)
>
> diff --git a/drivers/staging/comedi/comedidev.h b/drivers/staging/comedi/comedidev.h
> index 4eb2b77..5c78564 100644
> --- a/drivers/staging/comedi/comedidev.h
> +++ b/drivers/staging/comedi/comedidev.h
> @@ -43,11 +43,59 @@
>
> #include "comedi.h"
>
> -#define DPRINTK(format, args...) do { \
> - if (comedi_debug) \
> - printk(KERN_DEBUG "comedi: " format , ## args); \
> +#define comedi_printk(level, fmt, args...) \
> + printk(level "comedi: " pr_fmt(fmt), ##args)
> +
> +#define DPRINTK(format, args...) \
> +do { \
> + if (comedi_debug) \
> + comedi_printk(KERN_DEBUG, fmt, ##args); \
> } while (0)
>
> +#define comedi_emerg(fmt, ...) \
> + comedi_printk(KERN_EMERG, fmt, ##__VA_ARGS__)
I'd much rather you use the real dev_printk() versions of this instead
(dev_warn, dev_err, etc.) instead of creating a new macro.
thanks,
greg k-h
next prev parent reply other threads:[~2010-06-17 23:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 6:34 Henri Häkkinen
2010-06-17 23:02 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-12 11:04 Henri Häkkinen
2010-06-12 10:14 Henri Häkkinen
2010-06-13 2:14 ` Mark Rankilor
2010-06-13 5:07 ` Joe Perches
2010-06-13 5:30 ` Joe Perches
2010-06-13 11:27 ` Henri Häkkinen
2010-06-13 18:11 ` Joe Perches
2010-06-17 22:51 ` Greg KH
2010-06-17 23:15 ` Joe Perches
2010-06-17 23:28 ` Greg KH
2010-06-17 23:47 ` Joe Perches
2010-06-18 12:16 ` Ian Abbott
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=20100617230209.GA391@kroah.com \
--to=greg@kroah.com \
--cc=andrea.gelmini@gelma.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=henuxd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mithlesh@linsyssoft.com \
--cc=reodge@gmail.com \
--cc=wfp5p@virginia.edu \
/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
Powered by JetHome