linux-kernel - Re: [PATCH 10/10] added kernel build, configuration, and TODO files

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>] [day] [month] [year] [list]

Message-ID: <20141104180258.GB3940@kroah.com>
Date:	Tue, 4 Nov 2014 10:02:58 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	sostalle <sean.stalley@...el.com>
Cc:	Stephanie Wallick <stephanie.s.wallick@...el.com>,
	linux-kernel@...r.kernel.org, devel@...verdev.osuosl.org
Subject: Re: [PATCH 10/10] added kernel build, configuration, and TODO files

On Tue, Nov 04, 2014 at 09:55:19AM -0800, sostalle wrote:
> >On Mon, Nov 03, 2014 at 01:24:04PM -0800, Greg KH wrote:
> >>On Mon, Nov 03, 2014 at 12:42:57PM -0800, Stephanie Wallick wrote:
> >> --- /dev/null
> >> +++ b/drivers/staging/mausb/TODO
> >> @@ -0,0 +1,14 @@
> >> +TODO:
> >> +	- checkpatch.pl cleanups
> >
> >Is this still true?
> >
> 
> checkpatch.pl reports:
> total: 7 errors, 208 warnings, 10489 lines checked

Ok, fair enough.

> >And why does this need to be a staging driver?  What's wrong with making
> >it a "real" driver now?
> >
> 
> The short answer is: We don't think it's ready to be "real".
> 
> We didn't want to release it as a "real" driver because:
> 	- It's not stable enough yet.
> 	- It doesn't implement all the features required by the MA USB spec.
> 	- The MA USB spec isn't standalone. It requires a supplemental spec
> 	  to define media-specific behavior, like how MA USB packets are
> 	  encapsulated, how to discover MA USB devices on a network, etc.
> 	  So far, no media-specific specifications have been published.
> 	- There are no commercially-available Media Agnostic USB devices.
> 
> We wanted to release it to staging now because:
> 	- We have received requests from multiple companies for our host MA USB
> 	  driver. Putting it in staging seemed the best way to distribute it.
> 	- We feel that releasing what we have to staging now could promote
> 	  collaboration on one driver & help prevent duplicate work.

Ok, please include that information in the first email, it's much more
helpful :)

Can you resend this series, and cc: the linux-usb mailing list, and
address the "what about usbip?" questions as well?

thanks,

greg k-h
--
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/