On 05/01/2017 14:31, Adrian Chadd wrote:
There were lots of commits that could break things. :-)

Can you compile up some intermediary versions between 315141 and
r317559 to find which commit range broke things? That'll make chasing
it down much quicker!


FWIW I'm seeing this on the drm-next repository after the latest merge from upstream which happened on April 30th. I'll try to put some cycles into trying to find a range of potential commits that is causing this.


Pete Wright

freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to