<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [AMD tahiti XT] displayport broken" href="https://bugs.freedesktop.org/show_bug.cgi?id=107784#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [AMD tahiti XT] displayport broken" href="https://bugs.freedesktop.org/show_bug.cgi?id=107784">bug 107784</a> from <a class="email" href="mailto:felix.schwarz@oss.schwarz.eu" title="Felix Schwarz <felix.schwarz@oss.schwarz.eu>"> Felix Schwarz</a> <pre>(In reply to Sylvain BERTRAND from <a href="show_bug.cgi?id=107784#c9">comment #9</a>) > Ok, I got it. Since my git knowledge is quite limited, this "merge" commit is > opening a vast sea of new commits to test. > > I'll dive into bisection using bisect (which actually deals with those merge > commits). I am a bit scared of the amount of commits, may take hours/days. Don't worry: If your problem is immediately obvious after booting this should be not too bad. You can also use the versions you build manually to "seed" the git bisection process. That way you reduce the number of bisection steps a bit. If you encounter non-bootable kernels please use "git bisect skip" - this is important! DO NOT mark as "good"/"bad" in these cases. > Please, in the foreseable futur, do not make amd-staging-drm-next lag that > much. I think the "drm-next" thing was mandated by Linus so there is not much which can be done at this point. But anyway if you have an easily reproducible problem bisection is not too bad.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>