From: Stephen Warren <swarren@wwwdotorg.org>
To: manjunath.goudar@linaro.org
Cc: linux-usb@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
patches@linaro.org, stern@rowland.harvard.edu, arnd@linaro.org,
gregkh@linuxfoundation.org, Greg KH <greg@kroah.com>,
David Brown <davidb@codeaurora.org>,
Daniel Walker <dwalker@fifo99.com>,
Bryan Huntsman <bryanh@codeaurora.org>,
Brian Swetland <swetland@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/8] USB: EHCI: make ehci-msm a separate driver
Date: Mon, 11 Feb 2013 10:37:01 -0700 [thread overview]
Message-ID: <51192C3D.5050403@wwwdotorg.org> (raw)
In-Reply-To: <5117ee12.860e440a.097c.3521@mx.google.com>
On 02/10/2013 11:58 AM, manjunath.goudar@linaro.org wrote:
> Separate the Qualcomm On-Chip host controller driver from ehci-hcd host code
> diff --git a/drivers/usb/host/Kconfig b/drivers/usb/host/Kconfig
> @@ -203,7 +203,7 @@ config USB_EHCI_TEGRA
> boolean "NVIDIA Tegra HCD support"
> depends on USB_EHCI_HCD && ARCH_TEGRA
> select USB_EHCI_ROOT_HUB_TT
> - help
> + --- help---
> This driver enables support for the internal USB Host Controllers
> found in NVIDIA Tegra SoCs. The controllers are EHCI compliant.
I still don't think that's correct.
next prev parent reply other threads:[~2013-02-11 17:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1360522697-22902-1-git-send-email-y>
2013-02-10 18:58 ` [PATCH 2/8] USB: EHCI: make ehci-atmel a separate driver manjunath.goudar
2013-02-10 18:58 ` [PATCH 4/8] USB: EHCI: make ehci-mv " manjunath.goudar
2013-02-10 18:58 ` [PATCH 5/8] USB: EHCI: make ehci-vt8500 " manjunath.goudar
2013-02-10 18:58 ` [PATCH 6/8] USB: EHCI: make ehci-msm " manjunath.goudar
2013-02-11 17:37 ` Stephen Warren [this message]
2013-02-10 18:58 ` [PATCH 7/8] USB: EHCI: make ehci-w90X900 " manjunath.goudar
2013-02-10 18:58 ` [PATCH 8/8] USB: EHCI: make ehci-orion " manjunath.goudar
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=51192C3D.5050403@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=arnd@linaro.org \
--cc=bryanh@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=dwalker@fifo99.com \
--cc=greg@kroah.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=manjunath.goudar@linaro.org \
--cc=patches@linaro.org \
--cc=stern@rowland.harvard.edu \
--cc=swetland@google.com \
/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