lkml.org 
[lkml]   [2010]   [Jan]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: Memory probing fails after 2.6.30 (bisected)
From
On Wed, Jan 6, 2010 at 2:32 AM, Anders Eriksson <aeriksson@fastmail.fm> wrote:
>
> hancockrwd@gmail.com said:
>> Think you missed posting which was the actual bad commit it reported?
>
> The last one in the list:
> 8ecee4620e76aae418bfa0e8cc830e92cb559bbb
>
> That's a merge commit. How do i dig futher into that? My git-fu is lacking...

AFAIK, the bisect shouldn't land on a merge commit unless the changes
in the commit itself are what are causing the problem, and the merge
commit itself doesn't have any changes. Is it possible something went
wrong in the bisect and one of your good/bad results was incorrect?


\
 
 \ /
  Last update: 2010-01-07 00:55    [W:0.037 / U:0.604 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site