From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: [RFC] Patch to option HSO driver to the kernel Date: Mon, 14 Apr 2008 16:03:09 -0700 Message-ID: <20080414230309.GA1672@kroah.com> References: <20080414213238.GB28833@kroah.com> <20080414215905.GD16272@one-eyed-alien.net> <200804142342.08116.ajb@spheresystems.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Matthew Dharm , linux-usb@vger.kernel.org, netdev@vger.kernel.org, Alan Cox , Filip Aben , Paulius Zaleckas To: "Andrew Bird (Sphere Systems)" Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:51774 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752089AbYDNXDT (ORCPT ); Mon, 14 Apr 2008 19:03:19 -0400 Content-Disposition: inline In-Reply-To: <200804142342.08116.ajb@spheresystems.co.uk> Sender: netdev-owner@vger.kernel.org List-ID: On Mon, Apr 14, 2008 at 11:42:07PM +0100, Andrew Bird (Sphere Systems) wrote: > Hi Matthew, > I'd prefer the keep it as just 'hso' and change the textual description if > necessary. I think module names are just arbitrary, and should not > necessarily reflect the original usage too well, otherwise you end up with a > situation like with the 'option' module. That module is now used for many > devices from differing manufacturers and it doesn't really make much sense to > load the option module to service a device from Novatel, Sierra Wireless or > Huawei. Ok, that's fine with me, what should we use for the text in the driver and the Kconfig entry? thanks, greg k-h