public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: Dmitry Kasatkin <d.kasatkin@samsung.com>,
	linux-kernel@vger.kernel.org, dmitry.kasatkin@gmail.com
Subject: Re: [PATCH 2/2] xhci:prevent "callbacks suppressed" when debug is not enabled
Date: Fri, 16 Aug 2013 10:30:35 -0700	[thread overview]
Message-ID: <20130816173035.GA15607@kroah.com> (raw)
In-Reply-To: <20130816172635.GA7975@xanatos>

On Fri, Aug 16, 2013 at 10:26:35AM -0700, Sarah Sharp wrote:
> On Thu, Aug 15, 2013 at 05:17:16PM -0700, Greg KH wrote:
> > On Thu, Aug 15, 2013 at 07:04:55PM +0300, Dmitry Kasatkin wrote:
> > > When debug is not enabled and dev_dbg() will expand to nothing,
> > > log might be flooded with "callbacks suppressed". If it was not
> > > done on purpose, better to use dev_dbg_ratelimited() instead.
> > > 
> > > Signed-off-by: Dmitry Kasatkin <d.kasatkin@samsung.com>
> > > ---
> > >  drivers/usb/host/xhci-ring.c | 6 ++----
> > >  1 file changed, 2 insertions(+), 4 deletions(-)
> > 
> > 
> > Sarah, does this patch conflict with the trace debug patches being
> > worked on?  I'll hold off on applying it for now, let me know if it's ok
> > or not.
> 
> It doesn't conflict with the trace debug patches, because those only
> effect debugging with xhci_dbg with the host device, not dev_dbg with
> the USB device.  This should apply fine to usb-next.

Ok, can I get your ack for it so I can apply it?

thanks,

greg k-h

  parent reply	other threads:[~2013-08-16 17:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-15 16:04 [PATCH 1/2] dev-core: fix build break when DEBUG is enabled Dmitry Kasatkin
2013-08-15 16:04 ` [PATCH 2/2] xhci:prevent "callbacks suppressed" when debug is not enabled Dmitry Kasatkin
2013-08-16  0:17   ` Greg KH
2013-08-16 17:26     ` Sarah Sharp
2013-08-16 17:30       ` Sarah Sharp
2013-08-16 17:37         ` Greg KH
2013-08-16 17:38         ` Dmitry Kasatkin
2013-08-16 17:45           ` Greg KH
2013-08-16 17:50             ` Sarah Sharp
2013-08-27 14:16             ` Dmitry Kasatkin
2013-08-27 17:39               ` Greg KH
2013-08-27 17:40                 ` Dmitry Kasatkin
2013-08-16 17:30       ` Greg KH [this message]
2013-08-16 17:38         ` Sarah Sharp
2013-08-16 17:42           ` Dmitry Kasatkin
2013-08-15 16:37 ` [PATCH 1/2] dev-core: fix build break when DEBUG is enabled Greg KH
2013-08-15 16:53   ` Dmitry Kasatkin
2013-08-15 17:11     ` Greg KH

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=20130816173035.GA15607@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=d.kasatkin@samsung.com \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sarah.a.sharp@linux.intel.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