linux-kernel - Re: [PATCH RESEND 2/2] usb: host: tegra: Resetting PORT0 based on information received via DT.

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

Message-ID: <50F0B1CE.7050300@wwwdotorg.org>
Date:	Fri, 11 Jan 2013 17:43:58 -0700
From:	Stephen Warren <swarren@...dotorg.org>
To:	Greg KH <gregkh@...uxfoundation.org>
CC:	Venu Byravarasu <vbyravarasu@...dia.com>,
	stern@...land.harvard.edu, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND 2/2] usb: host: tegra: Resetting PORT0 based on
 information received via DT.

On 01/11/2013 05:14 PM, Greg KH wrote:
> On Thu, Jan 03, 2013 at 01:29:32PM -0700, Stephen Warren wrote:
>> On 01/03/2013 12:29 AM, Venu Byravarasu wrote:
>>> Tegra USB host driver is using port instance number,
>>> to handle some of the hardware issues on SOC e.g. reset PORT0
>>> twice etc. As instance number based handling looks ugly,
>>> making use of information passed through DT for achieving this.
>>>
>>> Signed-off-by: Venu Byravarasu <vbyravarasu@...dia.com>
>>> Acked-by: Alan Stern <stern@...land.harvard.edu>
>>
>> Greg, recall that I'm hoping to take this series through the Tegra tree
>> in order to manage EHCI/PHY/clock dependencies. I'm hoping to get your
>> ack if required, or is Alan's sufficient for this? Thanks.
> 
> Acked-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>

Thanks, applied to Tegra's for-3.9/usb branch.
--
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/