From: Greg KH <gregkh@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [GIT PATCH] USB patches for 2.6-git
Date: Fri, 17 Oct 2008 16:09:44 -0700 [thread overview]
Message-ID: <20081017230944.GA15344@suse.de> (raw)
In-Reply-To: <20081017230011.GA14185@suse.de>
On Fri, Oct 17, 2008 at 04:00:11PM -0700, Greg KH wrote:
> On Fri, Oct 17, 2008 at 03:47:58PM -0700, Linus Torvalds wrote:
> >
> >
> > On Fri, 17 Oct 2008, Greg KH wrote:
> > >
> > > Here is the big batch of USB patches for your 2.6-git tree.
> >
> > I really wish I were to get the occasional _clean_ pull for a change.
> >
> > f*ck me, but why do people keep adding more and more warnings, and
> > apparently not even bother to write clean code? The merge window is no
> > excuse for badly written crap.
> >
> > drivers/usb/host/ehci-hcd.c: In function ‘ehci_hcd_init’:
> > drivers/usb/host/ehci-hcd.c:1115: warning: label ‘err_debug’ defined but not used
>
> Why am I not seeing that warning here?
>
> ah, because I have debugging for USB enabled in my configuration, sorry
> about that, I should have caught that. That's the problem with doing a
> 'make allyesconfig' as a test build, I need to make it random at times
> to catch things like this.
In looking at that file closer, I can just remove all of the #ifdef
DEBUG options there, as there is no problem with them being always
built. The rest of the #ifdef mess in there is due to platform/hardware
configurations trying to share a common EHCI core.
thanks,
greg k-h
next prev parent reply other threads:[~2008-10-17 23:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 22:00 [GIT PATCH] USB patches for 2.6-git Greg KH
2008-10-17 22:47 ` Linus Torvalds
2008-10-17 23:00 ` Greg KH
2008-10-17 23:09 ` Greg KH [this message]
[not found] ` <gdfauh$hsp$1@ger.gmane.org>
2008-10-19 17:29 ` Greg KH
2008-10-19 19:37 ` Dmitry
-- strict thread matches above, loose matches on Subject: below --
2008-10-29 22:38 Greg KH
2008-11-13 23:02 Greg KH
2008-11-14 4:06 ` Gupta, Ajay Kumar
2008-11-14 19:15 ` Greg KH
2008-11-14 19:40 ` Sergei Shtylyov
2008-11-14 19:59 ` Greg KH
2008-11-14 20:10 ` Sergei Shtylyov
2008-11-14 20:55 ` Greg KH
2008-11-14 21:02 ` Sergei Shtylyov
2008-11-14 21:07 ` Greg KH
2008-12-17 19:27 Greg KH
2009-01-07 19:24 Greg KH
2009-01-07 20:23 ` Sergei Shtylyov
2009-01-07 21:28 ` Greg KH
2009-01-07 21:42 ` Sergei Shtylyov
2009-01-07 21:54 ` Andrew Morton
2009-01-07 22:48 ` David Brownell
2009-01-27 23:49 Greg KH
2009-01-27 23:56 ` Greg KH
2009-02-09 19:31 Greg KH
2009-02-27 22:45 Greg KH
2009-03-17 21:05 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=20081017230944.GA15344@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=torvalds@linux-foundation.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.