From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: [RFC/PATCH v3 2/5] uas: MS UAS Gadget driver - Infrastructure Date: Thu, 14 Apr 2011 10:40:07 -0700 Message-ID: <20110414174007.GA11640@kroah.com> References: <1302788176-27972-1-git-send-email-tlinder@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1302788176-27972-1-git-send-email-tlinder@codeaurora.org> Sender: linux-kernel-owner@vger.kernel.org To: Tatyana Brokhman Cc: gregkh@suse.de, linux-arm-msm@vger.kernel.org, ablay@codeaurora.org, balbi@ti.com, "open list:USB GADGET/PERIPH..." , open list List-Id: linux-arm-msm@vger.kernel.org On Thu, Apr 14, 2011 at 04:36:15PM +0300, Tatyana Brokhman wrote: > This patch implements the infrastructure for the UAS gadget driver. > The UAS gadget driver registers as a second configuration of the MS > gadet driver. > > A new module parameter was added to the mass_storage module: > bool use_uasp. (default = 0) > If this parameter is set to true, the mass_storage module will register > with the UAS configuration as the devices first configuration and > operate according to the UAS protocol. Ick, I'd _really_ prefer no new kernel module parameters. It gets messy and a pain to support and document (see you didn't document it...) Any way to do this "automatically"? Or some other way? thanks, greg k-h