From: Stephen Warren <swarren@wwwdotorg.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Venu Byravarasu <vbyravarasu@nvidia.com>,
Felipe Balbi <balbi@ti.com>,
grant.likely@secretlab.ca, rob.herring@calxeda.com,
rob@landley.net, linux@arm.linux.org.uk, sjg@chromium.org,
olof@lixom.net, linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH 1/2] arm: tegra: Add new DT property to USB node.
Date: Fri, 11 Jan 2013 17:43:52 -0700 [thread overview]
Message-ID: <50F0B1C8.400@wwwdotorg.org> (raw)
In-Reply-To: <20130112001414.GA21909@kroah.com>
On 01/11/2013 05:14 PM, Greg KH wrote:
> On Mon, Dec 17, 2012 at 05:04:41PM -0500, Alan Stern wrote:
>> On Mon, 17 Dec 2012, Stephen Warren wrote:
>>
>>> On 12/13/2012 11:59 PM, Venu Byravarasu wrote:
>>>> As Tegra USB host driver is using instance number for resetting
>>>> PORT0 twice, adding a new DT property for handling this.
>>>
>>> Alan, Greg, Felip,e
>>>
>>> This series looks fine to me.
>>>
>>> I'd like to take all the Tegra-related USB patches through the Tegra
>>> tree for 3.9 if possible (so I'm looking for your acks here). I believe
>>> Venu plans to significantly clean up the EHCI/PHY driver split for
>>> Tegra, rework the drivers, and add support for Tegra30 in addition to
>>> Tegra20. Some of this requires changes to some Tegra board files and
>>> device trees to maintain "git bisect" I don't know for sure yet, but I
>>> believe that rework may also end up conflicting with other clock-related
>>> rework that will show up for Tegra in 3.9. Are you OK with this? I'll
>>> certainly look for your review/acks on the patches before picking them
>>> up though.
>>
>> Regarding the changes to drivers/usb/host/ehci-tegra.c:
>>
>> Acked-by: Alan Stern <stern@rowland.harvard.edu>
>
> That's fine with me as well, feel free to think that I have now dropped
> all tegra-related patches from my queue, you can take them all :)
Thanks, applied to Tegra's for-3.9/usb branch.
next prev parent reply other threads:[~2013-01-12 0:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 6:59 [PATCH 0/2] usb: tegra: modifying port reset based on instance number Venu Byravarasu
2012-12-14 6:59 ` [PATCH 1/2] arm: tegra: Add new DT property to USB node Venu Byravarasu
2012-12-17 21:07 ` Stephen Warren
[not found] ` <50CF89AF.3000308-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-17 21:18 ` Greg KH
2012-12-17 22:06 ` Alan Stern
2012-12-17 22:04 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1212171704060.1409-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2013-01-12 0:14 ` Greg KH
2013-01-12 0:43 ` Stephen Warren [this message]
2012-12-14 6:59 ` [PATCH 2/2] usb: host: tegra: Resetting PORT0 based on information received via DT Venu Byravarasu
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=50F0B1C8.400@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=balbi@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=sjg@chromium.org \
--cc=stern@rowland.harvard.edu \
--cc=vbyravarasu@nvidia.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;
as well as URLs for NNTP newsgroup(s).