From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 87682] Horizontal lines in radeon driver on kernel 3.15 and upwards
Date: Tue, 03 May 2016 08:02:38 +0000 [thread overview]
Message-ID: <bug-87682-502-QXAHzfXHsj@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-87682-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 628 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=87682
--- Comment #6 from Felix Schwarz <felix.schwarz@oss.schwarz.eu> ---
(In reply to Thom from comment #5)
> I don't know what "git bisect" is but eager to learn.
"bisecting" is a way to find out which commit caused a specific regression.
This involves compiling the linux kernel from git and testing the compiled
versions. If you can find out which commit is the culprit chances are pretty
good that the problem can be fixed quickly.
To learn more about bisecting I suggest seaching for "git bisect".
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1525 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:[~2016-05-03 8:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-24 15:35 [Bug 87682] Horizontal lines in radeon driver on kernel 3.15 and upwards bugzilla-daemon
2014-12-24 15:38 ` bugzilla-daemon
2014-12-25 1:17 ` bugzilla-daemon
2014-12-25 12:37 ` bugzilla-daemon
2014-12-25 15:11 ` bugzilla-daemon
2015-01-05 17:24 ` bugzilla-daemon
2015-01-05 17:25 ` bugzilla-daemon
2016-05-02 23:10 ` bugzilla-daemon
2016-05-03 8:02 ` bugzilla-daemon [this message]
2016-05-04 9:39 ` bugzilla-daemon
2016-05-04 22:13 ` bugzilla-daemon
2016-05-05 17:01 ` bugzilla-daemon
2016-05-05 17:37 ` bugzilla-daemon
2016-05-06 2:25 ` bugzilla-daemon
2016-05-06 14:26 ` bugzilla-daemon
2016-05-09 9:26 ` bugzilla-daemon
2016-05-09 20:42 ` bugzilla-daemon
2016-05-10 1:42 ` bugzilla-daemon
2016-05-10 9:06 ` bugzilla-daemon
2016-05-10 22:12 ` bugzilla-daemon
2016-05-12 20:58 ` bugzilla-daemon
2016-06-14 8:03 ` bugzilla-daemon
2016-07-22 20:03 ` bugzilla-daemon
2016-07-22 22:34 ` bugzilla-daemon
2016-07-22 23:20 ` bugzilla-daemon
2016-07-23 21:02 ` bugzilla-daemon
2016-07-28 15:53 ` bugzilla-daemon
2016-07-28 16:23 ` 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-87682-502-QXAHzfXHsj@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