All of lore.kernel.org
 help / color / mirror / Atom feed
From: Potnuri Bharat Teja <bharat-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
To: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
Cc: SWise OGC
	<swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>,
	"dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
	<dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH for-next] iw_cxgb4: Change error/warn prints to pr_debug
Date: Fri, 29 Dec 2017 12:13:38 +0530	[thread overview]
Message-ID: <20171229064337.GA15043@chelsio.com> (raw)
In-Reply-To: <20171222173207.GF30884-uk2M96/98Pc@public.gmane.org>

On Friday, December 12/22/17, 2017 at 23:02:07 +0530, Jason Gunthorpe wrote:
> On Tue, Dec 19, 2017 at 04:32:54PM -0600, Steve Wise wrote:
> 
> > > > In general, I like module names in log statements, but we just
> > > > need to do it the right way to avoid the pr_debug issue...
> > > 
> > > Seems like a bigger problem than for linux-rdma?
> > > 
> > 
> > If redefining pr_fmt is actually the preferred way to add module names, then
> > I think pr_debug() might need
> > to be fixed.
> > 
> > > Shouldn't many of these prints be using dev_* stuff and be prefixed
> > > with their device name?
> > 
> > Yea, that makes sense.
> 
> Okay, I've dropped this patch.
> 
> The two changes to pr_debug should probably become dev_dbg, and
> resend?
For now I am resending the patch without pr_fmt change.
dev_dbg change would be an overall change if necessary.
> 
> Deal with the 'what should pr_fmt be' question someplace else :)
Agreed
> 
> Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-12-29  6:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 10:44 [PATCH for-next] iw_cxgb4: Change error/warn prints to pr_debug Potnuri Bharat Teja
     [not found] ` <1513680256-8153-1-git-send-email-bharat-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
2017-12-19 20:16   ` Jason Gunthorpe
     [not found]     ` <20171219201639.GA14814-uk2M96/98Pc@public.gmane.org>
2017-12-19 21:12       ` Steve Wise
2017-12-19 22:23         ` Jason Gunthorpe
     [not found]           ` <20171219222300.GH14814-uk2M96/98Pc@public.gmane.org>
2017-12-19 22:32             ` Steve Wise
2017-12-22 17:32               ` Jason Gunthorpe
     [not found]                 ` <20171222173207.GF30884-uk2M96/98Pc@public.gmane.org>
2017-12-29  6:43                   ` Potnuri Bharat Teja [this message]
     [not found]                     ` <20171229064337.GA15043-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
2017-12-29 18:09                       ` Jason Gunthorpe
  -- strict thread matches above, loose matches on Subject: below --
2017-12-19 10:08 Chelsio Cudbg
     [not found] ` <1513678108-6634-1-git-send-email-chelsiocudbg-KJX8L1YACloTKYOLMXNBRxrm3jAUxWOA@public.gmane.org>
2017-12-19 10:14   ` Potnuri Bharat Teja

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=20171229064337.GA15043@chelsio.com \
    --to=bharat-ut6up61k2wzbdgjk7y7tuq@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=jgg-uk2M96/98Pc@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.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 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.