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] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 18 Feb 2015 10:09:22 +0200
From:	Roger Quadros <rogerq@...com>
To:	Tony Lindgren <tony@...mide.com>, <kishon@...com>
CC:	<nm@...com>, <balbi@...com>, <george.cherian@...com>,
	<nsekhar@...com>, <linux-omap@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>
Subject: Re: [PATCH v3 0/4] phy: ti-pipe3: fixes for 3.19-rc

On 18/02/15 10:00, Roger Quadros wrote:
> On 13/01/15 17:54, Tony Lindgren wrote:
>> * Roger Quadros <rogerq@...com> [150113 04:26]:
>>> Hi,
>>>
>>> During system suspend L3INIT_960M_GFCLK and L3INIT_480M_GFCLK clocks remain
>>> active on the DRA7 platform. This is because the pipe3 driver doesn't shut
>>> them off as part of .suspend(). Patch 1 addresses this issue.
>>>
>>> SATA on both OMAP5 and DRA7 breaks when SATA drive is plugged in after a
>>> system suspend/resume or if AHCI_PLATFORM driver is used as module.
>>> Patches 2,3,4 fix it.
>>>
>>> Hope to get these patches in through the 3.19-rc cycle.
>>>
>>> Tony,
>>>
>>> Do you wish to take the DTS patches or let them go in through PHY tree?
>>
>> Those look ok to me to merge along with the fixes, will ack those two.
>>
> 
> Looks like this missed 3.19-rc. My bad for not following up.
> 
> Kishon, can you please queue these for 3.20-rc? Thanks.

Well the PHY patches (1 and 2) are already queued for v3.20-rc1 via Greg's usb-next tree.
Tony can you please queue the DT side patches for v3.20? Thanks.

cheers,
-roger
--
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/

Powered by blists - more mailing lists