<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [BSW] image corruption issue after edd849e5448c4f6ddc04a5fa1ac5479176660c27"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102818#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [BSW] image corruption issue after edd849e5448c4f6ddc04a5fa1ac5479176660c27"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102818">bug 102818</a>
from <span class="vcard"><a class="email" href="mailto:freedesktop@nmacleod.com" title="freedesktop@nmacleod.com">freedesktop@nmacleod.com</a>
</span></b>
<pre><span class="quote">> I don't see why git bisect wouldn't bisect into the merge.</span >
Sorry Jani, I'm not entirely sure what you mean here - I simply used "git
bisect" between 4.11.10 (known good) and 4.12-rc1 (known bad), and based on
testing of the resulting kernels git decided that the merge commit was the bad
commit.
Can you tell me the best way to bisect the merge commit and I'll give that a
go.
My kernel repo is a clone of
<a href="https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git">https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git</a>
<span class="quote">> Care to check the last results again?</span >
I'll ask the user to check the builds again, there were 14 in total. This may
take a few days. Unfortunately I can't reproduce this issue myself.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>