linux-kernel - RE: [RFC/PATCH v3 2/5] uas: MS UAS Gadget driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 16 Apr 2011 20:10:23 +0300
From:	"Tanya Brokhman" <tlinder@...eaurora.org>
To:	"'Greg KH'" <greg@...ah.com>
Cc:	<gregkh@...e.de>, <linux-arm-msm@...r.kernel.org>,
	<ablay@...eaurora.org>, <balbi@...com>,
	"'open list:USB GADGET/PERIPH...'" <linux-usb@...r.kernel.org>,
	"'open list'" <linux-kernel@...r.kernel.org>
Subject: RE: [RFC/PATCH v3 2/5] uas: MS UAS Gadget driver - Infrastructure

> >
> > 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




--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/