All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] USB device support for 2.5.8 (take 2)
Date: Tue, 16 Apr 2002 20:52:36 -0700	[thread overview]
Message-ID: <20020417035236.GC29897@kroah.com> (raw)
In-Reply-To: <20020417025104.GC29064@kroah.com> <Pine.LNX.4.33.0204162121060.13362-100000@home.transmeta.com>

On Tue, Apr 16, 2002 at 09:35:33PM -0700, Linus Torvalds wrote:
> 
> 
> On Tue, 16 Apr 2002, Greg KH wrote:
> >
> > Linus, here is an updated changeset series with the USB device support.
> 
> Since I haven't pulled any of the usb device updates yet, might I suggest:
> 
>  - redoing the BK archive completely without the broken series (ie an
>    actual "bk undo")

Well since you don't want to pull it, I can just trash this tree, it
only contains the Lineo code.

>  - explaining to me what a "usb device" is, that isn't a normal USB
>    device? Why is "usb/device/xxx" different from the existing USB device
>    drivers?

It's code to be a USB client device, not a USB host device, which is
what we currently have.  It is used in embedded devices that run Linux,
like the new Sharp device (can't remember the name right now...)

> In other words, please explain what the _point_ of this code is?
> Especially since the code is obvious crap, from the little I looked at it,
> and quite frankly my immediate reaction is that it shouldn't get even
> _close_ to the kernel before it has gone through some _major_ cleanup.
> 
> Let's face it, look at the absolute SHIT in usbd-debug.c, where somebody
> has re-created strcmp/strcpy/etc, except with stupid names, and bad
> implementation.
> 
> In short, I refuse to pull this crap. The people who wrote it were either
> on drugs, incompetent, or just plain crazy. "Just say no".

Sorry.  I spend most of my time on this code just cleaning the format
and removing build errors, instead of looking at the content :(

I'll work on fixing all of the crap before submitting it again.

thanks,

greg k-h

  reply	other threads:[~2002-04-17  4:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16 22:54 [BK PATCH] USB device support for 2.5.8 Greg KH
2002-04-16 22:58 ` Greg KH
2002-04-17  2:51 ` [BK PATCH] USB device support for 2.5.8 (take 2) Greg KH
2002-04-17  2:53   ` Greg KH
2002-04-17  4:35   ` Linus Torvalds
2002-04-17  3:52     ` Greg KH [this message]
2002-04-17  5:08       ` Linus Torvalds
2002-04-17 13:44         ` Greg KH
2002-04-17 16:00           ` [linux-usb-devel] " David Brownell
2002-04-17 17:57             ` Linus Torvalds
2002-04-17 18:08               ` Larry McVoy
2002-04-17 18:59                 ` Linus Torvalds
2002-04-17 18:14                   ` Greg KH
2002-04-17 18:17               ` Greg KH
2002-04-19  5:37                 ` George J Karabin
2002-04-19  5:46                   ` [linux-usb-devel] Re: [BK PATCH] USB device support for 2.5.8(take 2) Oliver Neukum
2002-04-19  6:11                     ` George J Karabin
2002-04-19 11:06                       ` [linux-usb-devel] Re: [BK PATCH] USB device support for2.5.8(take2) Oliver.Neukum
2002-04-19 16:22                         ` George J Karabin
2002-04-17 18:41               ` [linux-usb-devel] Re: [BK PATCH] USB device support for 2.5.8 (take 2) Stephen J. Gowdy
2002-04-17 18:31                 ` Greg KH
2002-04-17 18:44               ` [linux-usb-devel] Re: [BK PATCH] USB device support for 2.5.8 arjan
2002-04-17 19:02               ` [linux-usb-devel] Re: [BK PATCH] USB device support for 2.5.8 (take 2) Oliver Xymoron
2002-04-17 19:20               ` David Brownell
2002-04-17 20:07                 ` Johannes Erdfelt

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=20020417035236.GC29897@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=torvalds@transmeta.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 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.