The amd-stagint-4.11 doen't contain the commit ab51ee31dda1a37b473074e402394f879c51d591 in amd-staging-4.9

[Deucher, Alexander]

I guess it was just missed?  Was it committed before we switched to 4.11?  Once we switched to 4.11, all teams are responsible for making sure they land their patches in the current staging branch.

Alex

From: Liu, Monk
Sent: Tuesday, July 04, 2017 11:55 PM
To: Deng, Emily; Deucher, Alexander
Cc: amd-gfx at lists.freedesktop.org
Subject: RE: The amd-stagint-4.11 doen't contain the commit ab51ee31dda1a37b473074e402394f879c51d591 in amd-staging-4.9

+ amd-gfx

We really need to understand why this commit is not shown in 4.11 staging, because we worry other patches may meet same issue, and cause regression

BR Monk

From: Deng, Emily
Sent: Tuesday, July 04, 2017 11:31 PM
To: Deucher, Alexander <Alexander.Deucher at amd.com<mailto:Alexander.Deucher at amd.com>>; Liu, Monk <Monk.Liu at amd.com<mailto:Monk.Liu at amd.com>>
Subject: The amd-stagint-4.11 doen't contain the commit ab51ee31dda1a37b473074e402394f879c51d591 in amd-staging-4.9

Hi Alex,
     Monk has submitted a commit ab51ee31dda1a37b473074e402394f879c51d591 in amd-staging-4.9, but amd-staging-4.11 doesn't contain it.
     So is there any reason to prevent the commit being port to amd-staging-4.11? Or just missed this commit?

Best Wishes,
Emily Deng

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/amd-gfx/attachments/20170705/73852e2c/attachment.html>