All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Greg KH <greg@kroah.com>, Alex Chiang <achiang@hp.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] small xhci cleanups
Date: Tue, 16 Mar 2010 14:24:45 -0700	[thread overview]
Message-ID: <20100316212445.GA15729@xanatos> (raw)
In-Reply-To: <20100316204845.GJ8278@ldl.fc.hp.com> <20100309184723.GA31374@kroah.com>

On Tue, Mar 09, 2010 at 10:47:23AM -0800, Greg KH wrote:
> On Tue, Mar 09, 2010 at 11:32:27AM -0700, Alex Chiang wrote:
> > * Greg KH <greg@kroah.com>:
> > > On Tue, Mar 09, 2010 at 10:52:43AM -0700, Alex Chiang wrote:
> > > 
> > > >       USB: xhci: move all debug code under CONFIG_XHCI_HCD_DEBUGGING
> > > 
> > > Does this conflict with Sarah's other debugging patch she just sent out?
> > 
> > I'm assuming you're talking about this patch:
> > 
> > 	http://thread.gmane.org/gmane.linux.usb.general/28681
> 
> Yes.
> 
> > Yes, we'll definitely have conflicts. If you agree that we should
> > move the debug code under the Kconfig option, then the best
> > course of action would be for Sarah to rebase her work on top of
> > my patches (since they're intrusive).
> 
> As Sarah is the maintainer of the file, I'll leave that decision up to
> her :)
> 
> And keeping a config option for debugging isn't a good idea.  The rest
> of the kernel has switched to using dynamic debugging, so that distros
> and others can easily get information without requiring a kernel rebuild
> (which we can't expect users to always be able to do.)  So I would not
> recommend this change.
> 
> thanks,
> 
> greg k-h

On Tue, Mar 16, 2010 at 02:48:45PM -0600, Alex Chiang wrote:
> Naming consistency with other USB HCDs.
> 
> Signed-off-by: Alex Chiang <achiang@hp.com>
> ---
> Refreshed against 2.6.34-rc1 and compile tested.
> 
> I didn't refresh the debug one; waiting to hear back from Sarah
> to see if it's worth doing or not.

Ok, I didn't see Greg's email about dynamic debugging.  I guess you
shouldn't refresh the second patch.  I'm not sure how I would go about
converting the xHCI driver to dynamic debugging, as I haven't looked
into it.  Is there any documentation/simple examples?

Greg, does the less-verbose patch with log levels still make sense if
the driver got converted over to dynamic debugging?

Sarah Sharp

  reply	other threads:[~2010-03-16 21:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09 17:52 [PATCH 0/2] small xhci cleanups Alex Chiang
2010-03-09 17:52 ` [PATCH 1/2] USB: xhci: rename driver to xhci_hcd Alex Chiang
2010-03-16 19:03   ` Greg KH
2010-03-09 17:52 ` [PATCH 2/2] USB: xhci: move all debug code under CONFIG_XHCI_HCD_DEBUGGING Alex Chiang
2010-03-09 18:14 ` [PATCH 0/2] small xhci cleanups Greg KH
2010-03-09 18:32   ` Alex Chiang
2010-03-09 18:47     ` Greg KH
2010-03-16 21:24       ` Sarah Sharp [this message]
2010-03-16 21:40         ` Greg KH
2010-03-18 21:33           ` Sarah Sharp
2010-03-18 21:50             ` Roland Dreier
2010-03-18 22:19             ` Greg KH
2010-03-18 22:30               ` Roland Dreier
2010-03-18 22:54               ` Sarah Sharp
  -- strict thread matches above, loose matches on Subject: below --
2010-03-16 20:48 [PATCH v2] USB: xhci: rename driver to xhci_hcd Alex Chiang
2010-03-16 21:09 ` Sarah Sharp
2010-03-17  2:22 ` Crane Cai
2010-03-17  4:30   ` 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=20100316212445.GA15729@xanatos \
    --to=sarah.a.sharp@linux.intel.com \
    --cc=achiang@hp.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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 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.