From: "Tanya Brokhman" <tlinder@codeaurora.org>
To: 'Greg KH' <greg@kroah.com>
Cc: gregkh@suse.de, linux-usb@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: RE: [PATCH v4 0/4] usb gadget: Add SuperSpeed support to the Gadget Framework
Date: Fri, 19 Nov 2010 12:56:22 +0200 [thread overview]
Message-ID: <000701cb87d8$698fab60$3caf0220$@org> (raw)
In-Reply-To: <20101118154848.GC1719@kroah.com>
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.
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?
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?
I'm new at this so sorry for troubling you with extra explanations.
Thanks for your patience and guidance
Regards,
Tanya Brokhman
Consultant for Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
-----Original Message-----
From: Greg KH [mailto:greg@kroah.com]
Sent: Thursday, November 18, 2010 5:49 PM
To: Tatyana Brokhman
Cc: gregkh@suse.de; linux-usb@vger.kernel.org; linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v4 0/4] usb gadget: Add SuperSpeed support to the Gadget
Framework
On Thu, Nov 18, 2010 at 02:46:16PM +0200, Tatyana Brokhman wrote:
> This patch series adds the SuperSpeed functionality to the gadget
framework.
> This implementation passed both USBCV 3.0 and 2.0 test suites.
Do you have a pointer to the tests that you mentioned previously? It
would be good to include them here as well.
> Rebased on top of v2.6.37-rc1
I would need them on top of linux-next if I were to be able to accept
them.
thanks,
greg k-h
next prev parent reply other threads:[~2010-11-19 10:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 12:46 [PATCH v4 0/4] usb gadget: Add SuperSpeed support to the Gadget Framework Tatyana Brokhman
2010-11-18 15:48 ` Greg KH
2010-11-19 10:56 ` Tanya Brokhman [this message]
2010-11-19 17:25 ` Greg KH
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='000701cb87d8$698fab60$3caf0220$@org' \
--to=tlinder@codeaurora.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-arm-msm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.