On Wed, Nov 22, 2017 at 8:40 AM, Christian Zigotzky <chzigot...@xenosoft.de> wrote: > On 22 November 2017 at 2:27PM, Ilia Mirkin wrote: >> >> On Wed, Nov 22, 2017 at 8:20 AM, Christian Zigotzky >> <chzigot...@xenosoft.de> wrote: >>> >>> Hi Alex, >>> >>> I reverted the following files in the first bad commit (first DRM >>> updates) >> >> Is the merge commit really the first bad commit? i.e. both parents of >> the merge are good, but the merge commit itself is bad? Or did you do >> this manually and therefore didn't go into the merge parents? If so, >> I'd recommend doing a proper bisect (search for "git bisect", there >> are tons of guides). That will identify the commit that's actually >> responsible. > > Hi ilia, > > I did it manually. If I revert the merge commit then the hardware 3D > acceleration works. Is it possible to bisect in the merge commit directly?
I thought I covered that... "I'd recommend doing a proper bisect (search for "git bisect", there are tons of guides). That will identify the commit that's actually responsible." -ilia _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
