From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100663] commit 61e47d92c5196 breaks RS780
Date: Wed, 12 Apr 2017 14:42:44 +0000 [thread overview]
Message-ID: <bug-100663-502-rEIURpSUCD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100663-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 911 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100663
octoploid <octoploid@yandex.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Hi-Angel@yandex.ru
Summary|mesa trunk breaks RS780 |commit 61e47d92c5196 breaks
| |RS780
--- Comment #3 from octoploid <octoploid@yandex.com> ---
Well, I figured out a way to bisect without rebooting.
The issue started with:
61e47d92c5196bf0240e322bb1b9d305836559e3 is the first bad commit
commit 61e47d92c5196bf0240e322bb1b9d305836559e3
Author: Constantine Kharlamov <Hi-Angel@yandex.ru>
Date: Mon Apr 10 23:04:37 2017 +0300
r600g: get rid of dummy pixel shader
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2322 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-04-12 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 12:33 [Bug 100663] mesa trunk breaks RS780 bugzilla-daemon
2017-04-12 13:17 ` bugzilla-daemon
2017-04-12 13:53 ` bugzilla-daemon
2017-04-12 14:42 ` bugzilla-daemon [this message]
2017-04-12 15:50 ` [Bug 100663] commit 61e47d92c5196 " bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-100663-502-rEIURpSUCD@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox