<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [IT6506 Display Receiver] DP hotplug fails (display and audio) with i915/kernel 3.11.1" href="https://bugs.freedesktop.org/show_bug.cgi?id=70301#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [IT6506 Display Receiver] DP hotplug fails (display and audio) with i915/kernel 3.11.1" href="https://bugs.freedesktop.org/show_bug.cgi?id=70301">bug 70301</a> from <a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> Daniel Vetter</a> <pre>(In reply to <a href="show_bug.cgi?id=70301#c5">comment #5</a>) > Created <a href="attachment.cgi?id=87577" name="attach_87577" title="git bisect log info - intel_dp.c/v3.9.5-v3.10.10">attachment 87577</a> <a href="attachment.cgi?id=87577&action=edit" title="git bisect log info - intel_dp.c/v3.9.5-v3.10.10">[details]</a> > git bisect log info - intel_dp.c/v3.9.5-v3.10.10 > > 1. The total commits regarding intel_dp.c between v3.9.5 and v3.10.10 are > about 44 records (see git_bisect_v3.9.5_v3.10.10_intel_dp.log that I > attached to this thread) > 2. Please advise if you have any suggestions to improve the trial and error > process. git bisect won't let you test all 44 commits, but it uses a binary search on the history, so should only be about 5-6 revsisions for testing. That's the reason why bisecting of entire kernel releases (with a few 10k commits) is possible, but restricting the search space to specific files like here always helps. git will also tell you how many steps are left after each testing round.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>