[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200403102928.GA3539@duo.ucw.cz>
Date: Fri, 3 Apr 2020 12:29:31 +0200
From: Pavel Machek <pavel@....cz>
To: kernel list <linux-kernel@...r.kernel.org>,
jani.nikula@...ux.intel.com, joonas.lahtinen@...ux.intel.com,
rodrigo.vivi@...el.com, intel-gfx@...ts.freedesktop.org,
airlied@...hat.com
Cc: tglx@...utronix.de, mingo@...hat.com, bp@...en8.de, hpa@...or.com
Subject: Re: 5.7-rc0: regression caused by drm tree, hangs while attempting
to run X
Hi!
> > commit f365ab31efacb70bed1e821f7435626e0b2528a6
> > Merge: 4646de87d325 59e7a8cc2dcf
> > Author: Linus Torvalds <torvalds@...ux-foundation.org>
> > Date: Wed Apr 1 15:24:20 2020 -0700
> >
> > Merge tag 'drm-next-2020-04-01' of
> > git://anongit.freedesktop.org/drm/drm
> Any ideas, besides the b-word?
>
> Would c0ca be good commit for testing?
>
> commit 700d6ab987f3b5e28b13b5993e5a9a975c5604e2
> Merge: c0ca5437c509 2bdd4c28baff
c0ca is broken.
commit 9001b17698d86f842e2b13e0cafe8021d43209e9
Merge: bda1fb0ed000 217a485c8399
Merge tag 'drm-intel-next-2020-03-13' of git://anongit.freedesktop.org/drm/d
rm-intel into drm-next
UAPI Changes:
So bda1fb0ed000 looks like test candidate... and that one works.
I guess 217a485c8399 is reasonable next step... and that
11a48a5a18c63fd7621bb050228cebf13566e4d8 should work ok.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)
Powered by blists - more mailing lists