On Wed, Dec 13, 2017 at 8:57 AM, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Wed, Dec 13, 2017 at 07:48:43AM +0100, Marek Szyprowski wrote:
Hi Shuah and Greg,
On 2017-12-12 15:47, Shuah Khan wrote:
On 12/12/2017 05:43 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.6 release. There are 164 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Thu Dec 14 12:34:08 UTC 2017. Anything received after that time might be too late.
The whole patch series can be found in one patch at: kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.6-rc1.gz or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.14.y and the diffstat can be found below.
thanks,
greg k-h
Daniel Vetter daniel.vetter@ffwll.ch drm: safely free connectors from connector_iter
Marek Szyprowski m.szyprowski@samsung.com drm/bridge: analogix dp: Fix runtime PM state in get_modes() callback
The above two patches have been found to be the cause of boot hang on exynos Peach Pi(t) chromebooks.
I am adding Daniel and Marek to the thread.
The deadlock is caused by the Daniels patch. My patch only changes the order of device initialization what might hide or reveal bug related to Daniels patch.
So should I revert Daniel's patch? Or is there already a fix for that in Linus's tree?
Not yet, still typing it. Hopefully all in time for -rc4. I think reverting it for now should be ok, I'll annotate the cc: stable lines for the new ones with a note that you need to re-cherry-pick it to make it all work. -Daniel