Hi Alexander, On Sun, 8 Sep 2019 17:13:07 +0300 Alexander Kapshuk <alexander.kapshuk@xxxxxxxxx> wrote: > > This is my first bisect. Here's what I've tried so far and based on the > output I got, I seem to be taken in the opposit direction. > > git bisect start > git bisect bad # 7dc4585e0378:next-20190903 > git bisect good next-20190730 #70f4b4ac1655 If you are bisecting linux-next, I will suggest bisecting between the stable branch on linux-next (which is just Linus' tree when I started that day) and the top of the first linux-next that fails. (Assuming that the stable branch is good). so git bisect start git bisect good stable git bisect bad next-20190903 and go from there. It will (unfortunately) be quite a few commits to test :-( -- Cheers, Stephen Rothwell
Attachment:
pgpJY4QagPhgz.pgp
Description: OpenPGP digital signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
