Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 19 Apr 2002 07:07:01 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 19 Apr 2002 07:07:00 -0400 Received: from mailrelay1.lrz-muenchen.de ([129.187.254.101]:29255 "EHLO mailrelay1.lrz-muenchen.de") by vger.kernel.org with ESMTP id ; Fri, 19 Apr 2002 07:06:59 -0400 Date: Fri, 19 Apr 2002 13:06:47 +0200 (MET DST) From: Oliver.Neukum@lrz.uni-muenchen.de X-X-Sender: ui222bq@sun3.lrz-muenchen.de To: George J Karabin cc: Oliver Neukum , Greg KH , Linus Torvalds , David Brownell , , Subject: Re: [linux-usb-devel] Re: [BK PATCH] USB device support for2.5.8(take2) In-Reply-To: <1019196683.1733.34.camel@pane.chasm.dyndns.org> Message-Id: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > That said, target or client or anything else distinctive sounds fine > too. I'm just partial to the spec-derived-naming idea. (Although I > really wish the USB spec folks could have come up with two names that > were more descriptively different...) Why you do you want to derive a name from the specs ? Someone who has read them will no what is refered to whatever we name it. The significance of a the name is important to those who look into usb code occasionaly. These typically haven't read the spec. Regards Oliver - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/