From: sylvain.bertrand@gmail.com
To: bugzilla-daemon@freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Bug 107784] [AMD tahiti XT] displayport broken
Date: Thu, 6 Sep 2018 21:10:18 +0000 [thread overview]
Message-ID: <20180906211018.GA370@freedom> (raw)
In-Reply-To: <bug-107784-502-a1Z7Ydo2iF@http.bugs.freedesktop.org/>
Got something, sort of obvious for a human, impossible for bisect to know,
which explains why this bisection was a failure:
testing a commit in the middle of a series of commits which are to be taken as
a whole to be consistent for normal operations of the kernel, is wrong. That,
bisect cannot know.
In my case, the TSC commits are "good"... and testing time has nothing to do
with this: testing a commit in the middle of this series will have a side
effect (DP link/aux timings...) on what I am observing to decide if a commit is
"bad" or "good". In my case it will break this observable (my DP monitor is
_really_ not working) and I'll tag the commit as "bad", which is inconsistent.
The bottom of this, which is _obvious_ for an experienced git user on large
projects, at the time of big merges on the main branch of a project like linux,
if something breaks, bisect is probably more your enemy than your friend: it is
ok to ask "Can you bisect?" on a sub-sub-system branch which has been free from
big merges from any related other subsystems for a good while, but almost an
insult on such massive update.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-09-06 21:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 17:22 [Bug 107784] [AMD tahiti XT] displayport broken bugzilla-daemon
2018-09-02 17:28 ` bugzilla-daemon
2018-09-03 9:17 ` bugzilla-daemon
2018-09-03 10:30 ` bugzilla-daemon
2018-09-03 14:55 ` bugzilla-daemon
2018-09-05 7:19 ` bugzilla-daemon
2018-09-05 11:50 ` bugzilla-daemon
2018-09-05 12:28 ` bugzilla-daemon
2018-09-05 12:33 ` bugzilla-daemon
2018-09-05 13:38 ` sylvain.bertrand
2018-09-05 13:38 ` bugzilla-daemon
2018-09-05 17:44 ` bugzilla-daemon
2018-09-05 21:48 ` sylvain.bertrand
2018-09-05 21:48 ` bugzilla-daemon
2018-09-05 21:52 ` bugzilla-daemon
2018-09-05 21:54 ` bugzilla-daemon
2018-09-06 10:04 ` bugzilla-daemon
2018-09-06 12:31 ` sylvain.bertrand
2018-09-06 12:31 ` bugzilla-daemon
2018-09-06 14:22 ` bugzilla-daemon
2018-09-06 16:20 ` sylvain.bertrand
2018-09-06 16:20 ` bugzilla-daemon
2018-09-06 21:10 ` sylvain.bertrand [this message]
2018-09-07 21:48 ` sylvain.bertrand
2018-09-06 21:10 ` bugzilla-daemon
2018-09-07 21:48 ` bugzilla-daemon
2018-09-09 3:45 ` sylvain.bertrand
2018-09-09 3:46 ` bugzilla-daemon
2018-09-09 5:57 ` bugzilla-daemon
2018-09-09 13:05 ` bugzilla-daemon
2018-09-09 13:11 ` bugzilla-daemon
2018-09-09 14:59 ` sylvain.bertrand
2018-09-09 14:59 ` bugzilla-daemon
2018-09-10 5:20 ` bugzilla-daemon
2018-09-10 9:15 ` 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=20180906211018.GA370@freedom \
--to=sylvain.bertrand@gmail.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.