Well the switch over to 4.11 was made in quite a haste while Alex was on vacation. I've did my best to cherry-pick everything over from 4.9 to 4.11, but it is entirely possible that the patch was either missed accidentally or committed after the switch to 4.11. Christian. Am 05.07.2017 um 15:29 schrieb 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**//* > > > > _______________________________________________ > amd-gfx mailing list > amd-gfx at lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/amd-gfx -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/amd-gfx/attachments/20170705/484dcc5c/attachment.html>
