mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Ramprasad Chinthekindi <Ramprasad.Chinthekindi@hgst.com>
Cc: OS Engineering <osengineering@stec-inc.com>,
	"axboe@kernel.dk" <axboe@kernel.dk>,
	Akhil Bhansali <Akhil.Bhansali@hgst.com>,
	"jmoyer@redhat.com" <jmoyer@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Amit Phansalkar <Amit.Phansalkar@hgst.com>
Subject: Re: [PATCH 1/2] skd: Replaced custom debug PRINTKs with pr_debug
Date: Thu, 03 Oct 2013 09:14:44 -0700	[thread overview]
Message-ID: <1380816884.2081.113.camel@joe-AO722> (raw)
In-Reply-To: <24CA9A5C93173F48A9E3313B866A7C280F1C10@MYMBX3.stec-inc.ad>

On Thu, 2013-10-03 at 10:09 +0000, Ramprasad Chinthekindi wrote:
> > -----Original Message-----
> > On Tue, 2013-10-01 at 12:25 +0000, OS Engineering wrote:
> > > Hi Jens,
> > > I'm sending a patch to replace custom debug macros with pr_debug().
> > Kindly please review the patch.
> > > Thanking you.
> > 
> > I think that this doesn't differentiate between
> > the 2 debugging levels currently implemented.
> > 
> > I'd do something like this:
> > 
> > Add pr_fmt to prefix pr_<level> uses with "skd: "
> > Add skd_<level> convenience logging macros
> > Convert VPRINTK/DPRINTK to skd_dbg(level, skdev, fmt, ...)
> > Convert pr_<level>("(%s): ...", skd_name(skdev), ...) uses to
> > 	skd_<level>(skdev, ...)
> > Use kcalloc not kzalloc with multiply
> > Remove a couple unnecessary pr_err function logging uses
> > Add missing newline to logging
[]
> Jens Axboe and other community members suggested us to remove the custom PRINTK macros from driver and replace them with pr_* macros directly.
> From driver's perspective, it's perfectly fine not to distinguish VPRINTs and DPRINTs. Hence, both have been replaced with pr_debug().

The initial patch net adds ~120 line of code,
the suggested patch net removes ~50 and
consolidates a few different output styles.

Also, please don't quote the entire patch
without commenting on it.  Delete the
quoted stuff that's not relevant please.


      reply	other threads:[~2013-10-03 16:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-01 12:25 OS Engineering
2013-10-01 18:33 ` Joe Perches
2013-10-03 10:09   ` Ramprasad Chinthekindi
2013-10-03 16:14     ` Joe Perches [this message]

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=1380816884.2081.113.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=Akhil.Bhansali@hgst.com \
    --cc=Amit.Phansalkar@hgst.com \
    --cc=Ramprasad.Chinthekindi@hgst.com \
    --cc=axboe@kernel.dk \
    --cc=jmoyer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=osengineering@stec-inc.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

all inboxes | Powered by JetHome®