From: "Tanya Brokhman" <tlinder@codeaurora.org>
To: "'Greg KH'" <greg@kroah.com>
Cc: <gregkh@suse.de>, <linux-arm-msm@vger.kernel.org>,
<ablay@codeaurora.org>, <balbi@ti.com>,
"'open list:USB GADGET/PERIPH...'" <linux-usb@vger.kernel.org>,
"'open list'" <linux-kernel@vger.kernel.org>
Subject: RE: [RFC/PATCH v3 2/5] uas: MS UAS Gadget driver - Infrastructure
Date: Sat, 16 Apr 2011 20:10:23 +0300 [thread overview]
Message-ID: <003501cbfc59$2eab53a0$8c01fae0$@org> (raw)
In-Reply-To: <20110414174007.GA11640@kroah.com>
> >
> > 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,
We've added this parameter as a first development phase to help us in
debugging/testing. The gadget driver is functional and feature complete at
the moment but we're still working on some improvements and further testing.
The module parameter will be removed in the final version.
Best regards,
Tanya Brokhman
Consultant for Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next prev parent reply other threads:[~2011-04-16 17:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 13:36 [RFC/PATCH v3 2/5] uas: MS UAS Gadget driver - Infrastructure Tatyana Brokhman
2011-04-14 17:31 ` Alan Stern
2011-04-14 17:40 ` Greg KH
2011-04-16 17:10 ` Tanya Brokhman [this message]
2011-04-14 17:41 ` Greg KH
2011-04-18 19:37 ` Sarah Sharp
2011-04-19 10:30 ` Tanya Brokhman
2011-04-26 9:00 ` Tanya Brokhman
2011-04-26 17:25 ` Sarah Sharp
2011-04-26 18:40 ` Alan Stern
2011-04-26 20:06 ` Sarah Sharp
2011-04-26 20:59 ` Greg KH
2011-04-27 17:16 ` Alan Stern
2011-04-28 5:54 ` Tanya Brokhman
2011-04-28 14:13 ` Alan Stern
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='003501cbfc59$2eab53a0$8c01fae0$@org' \
--to=tlinder@codeaurora.org \
--cc=ablay@codeaurora.org \
--cc=balbi@ti.com \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).