Re: [PATCH v4 0/4] usb gadget: Add SuperSpeed support to the Gadget Framework

[Greg KH <gregkh@suse.de>]

A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Fri, Nov 19, 2010 at 12:56:22PM +0200, Tanya Brokhman wrote:
> Hi Greg
> 
> Unfortunately I can't add a pointer to the unittest I mentioned since we
> didn't release them yet. It's in our TODO list but we didn't get to it yet
> since if we're about to release them we need to go over the code again as it
> won't be excepted as is due to coding style issues. 

Coding style issues only take a few hours to resolve, that's not a good
excuse :)

> I have a question regarding sharing this test code: 
> As I mentioned earlier (in another thread) the tests are written using the
> GoogleTest Framework and libusb so as you already understood - it's a user
> space application. If we were to share them, how is it done? It seems that
> linux-usb@vger isn't the most appropriate mailing list for this. Or is it?
> Also, we added several patches on top of the libusb (think the latest
> version but not sure) that also need to be released for that.
> Bottom line is: In order to use these test one will need the following
> patches:
> 1. Several updates on top of the libusb branch
> 2. The user-space code
> 3. several patches on top of the v2.6.36 (or later) that implement the needs
> testing functionality on the kernel side (for example: new control message
> was added to dummy_hcd to perform connect/disconnect test)
> 
> How this should be released?

How ever you can.  Seriously, point people at all of the above that you
have, and then work with the libusb people to get the needed changes
into their tree, which, if the patches are reasonable, shouldn't be hard
at all.

> I'm sorry but I'm not familiar with linux-next that you mentioned. I thought
> v2.6.37-rc1 is the latest. Could you please provide me with more details on
> linux-next branch and a pointer to it?

google linux-next to see the FAQ and find out how to download it.

Also, please read the Documentation/development_process/ files to
understand a bit more about how the kernel development process works.
If you have further questions after reading that, please let us know.

hope this helps,

greg k-h