public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "L. Alberto Giménez" <agimenez@sysvalve.es>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
	Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [PATCH 3/3] Staging: rt2860: include KERN_* in printk
Date: Sun, 12 Dec 2010 20:25:54 +0100	[thread overview]
Message-ID: <20101212192554.GA32583@bart.evergreen.loc> (raw)
In-Reply-To: <1292180668.18202.43.camel@Joe-Laptop>

On Sun, Dec 12, 2010 at 11:04:28AM -0800, Joe Perches wrote:
> On Sun, 2010-12-12 at 18:56 +0100, L. Alberto Giménez wrote:
> > Fix checkpatch complains
> > diff --git a/drivers/staging/rt2860/common/ee_efuse.c b/drivers/staging/rt2860/common/ee_efuse.c
> []
> > @@ -281,8 +281,8 @@ int set_eFusedump_Proc(struct rt_rtmp_adapter *pAd, char *arg)
> >  
> >  		eFuseReadPhysical(pAd, &InBuf[0], 4, &InBuf[2], 2);
> >  		if (i % 4 == 0)
> > -			printk("\nBlock %x:", i / 8);
> > -		printk("%04x ", InBuf[2]);
> > +			printk(KERN_DEBUG "\nBlock %x:", i / 8);
> > +		printk(KERN_DEBUG "%04x ", InBuf[2]);
> >  	}
> >  	return TRUE;
> >  }
> 
> Not quite.  Use:
> [...]

Ok.

> > diff --git a/drivers/staging/rt2860/pci_main_dev.c b/drivers/staging/rt2860/pci_main_dev.c
> >[...]
> > -#ifdef DEBUG
> > -		printk("RTMPAllocateNdisPacket Fail\n");
> > -#endif
> > +		printk(KERN_DEBUG "RTMPAllocateNdisPacket Fail\n");
> 
> Behavior change.
> Using pr_devel would be exactly the same.
> Using pr_debug would enable dynamic debug.

You are completely right. I guessed that DEBUG would be a developer-defined
definition. Will fix with pr_devel, makes more sense to me.

> 
> > @@ -601,15 +600,15 @@ void hex_dump(char *str, unsigned char *pSrcBufVA, unsigned int SrcBufLen)
> >[...]
> This should use print_hex_dump

Ok, but I'll have to figure out how to translate the arguments without losing
the original developers intended format.

> 
> > diff --git a/drivers/staging/rt2860/rt_linux.h b/drivers/staging/rt2860/rt_linux.h
> []
> >  #define DBGPRINT_ERR(Fmt)           \
> >  {                                   \
> > -    printk("ERROR! ");          \
> > +    printk(KERN_ERR "ERROR! ");          \
> >      printk Fmt;                  \
> >  }
> 
> Better ways to do this:
> 
> #define DBGPRINT_ERR(fmt, args...) printk(KERN_ERR fmt, ##args)
> or
> #define DBGPRINT_ERR(fmt, ...) printk(KERN_ERR fmt, ##__VA_ARGS__)

Thanks for your review. Will resend.


Regards,

-- 
L. Alberto Giménez
JabberID agimenez@jabber.sysvalve.es
GnuPG key ID 0x3BAABDE1

  reply	other threads:[~2010-12-12 19:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12 17:56 [PATCH 0/3] Staging: rt2860: Fix checkpatch issues L. Alberto Giménez
2010-12-12 17:56 ` [PATCH 1/3] Staging: rt2860: Clean spaces before tabs L. Alberto Giménez
2010-12-13  6:05   ` Dan Carpenter
2010-12-12 17:56 ` [PATCH 2/3] Staging: rt2860: Avoid extern in .c file L. Alberto Giménez
2010-12-12 17:56 ` [PATCH 3/3] Staging: rt2860: include KERN_* in printk L. Alberto Giménez
2010-12-12 19:04   ` Joe Perches
2010-12-12 19:25     ` L. Alberto Giménez [this message]
2010-12-12 19:46       ` Joe Perches
2010-12-13  0:01         ` L. Alberto Giménez
2010-12-13  3:13           ` Joe Perches
2010-12-13  5:56     ` Dan Carpenter
2010-12-13  6:03       ` Joe Perches
2010-12-12 23:58   ` [PATCH v2] " L. Alberto Giménez
2010-12-13 18:30     ` Greg KH
2010-12-13 20:24       ` L. Alberto Giménez
2010-12-13 21:15         ` Greg KH
2010-12-13 21:53           ` Joe Perches
2010-12-13 22:17             ` Greg KH
2010-12-14  1:01               ` [PATCH 1/2][RESEND] " L. Alberto Giménez
2010-12-14  1:01               ` [PATCH 2/2][RESEND] Staging: rt2860: Sanitize DBGPRINT_ERR macro L. Alberto Giménez

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=20101212192554.GA32583@bart.evergreen.loc \
    --to=agimenez@sysvalve.es \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@suse.de \
    --cc=joe@perches.com \
    --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