From arequipeno at gmail.com  Mon Jul 13 00:28:23 2020
From: arequipeno at gmail.com (Ian Pilcher)
Date: Sun, 12 Jul 2020 19:28:23 -0500
Subject: [Dri-users] Bisecting a DRM issue in merged commits
Message-ID: <reg9r7$ore$1@ciao.gmane.io>

Somewhere between Linux 5.6 and Linux 5.7, one of the displays attached
to my Dell TB16 dock stopped working.  (X appears to think that it's
working, based on the output of xrandr, but it doesn't actually display
anything.)

I've bisect the mainline kernel, and identified the following "bad"
commit:

commit ff36e78fdb251b9fa65028554689806961e011eb
Merge: 143d9c3e7b6a 1b245ec5b685
Author: Rodrigo Vivi <rodrigo.vivi at intel.com>
Date:   Tue Feb 25 09:29:58 2020 -0800

     Merge drm/drm-next into drm-intel-next-queued

     Some DSI and VBT pending patches from Hans will apply
     cleanly and with less ugly conflicts if they are rebuilt
     on top of other patches that recently landed on drm-next.

     Reference: https://patchwork.freedesktop.org/series/70952/
     Cc: Hans de Goede <hdegoede at redhat.com>
     Signed-off-by: Rodrigo Vivi <rodrigo.vivi at intel.com

However, this doesn't seem to actually be a single commit, and I'm not
sufficiently familiar with git to know how to proceed.

Any pointers on how to get a useful result out of git bisect would be
greatly appreciated.

Thanks!

-- 
========================================================================
                  In Soviet Russia, Google searches you!
========================================================================