DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=BZL7DzX19fOPX7zS09m4+H73s2JHMINZ2HkFdWQ6M9wHuOV3jFLDPJoSj1SYvwb5TR
         LyQlzWReE2hPtjZMmMmOn0VkOhVnPkiQS2+Nw8vtNX2HcF/YxsmdsMqq0hvUbLAJxMDe
         JNriNHCoOfEA1Wy8wbpWYRq/CHQ8waNj/fNFA=
MIME-Version: 1.0
In-Reply-To: <20100106083214.DAAA933C5F5@tippex.mynet.homeunix.org>
References: <20100105110256.D2DF133C4B0@tippex.mynet.homeunix.org>
	 <4B43DF97.7080208@gmail.com>
	 <20100106083214.DAAA933C5F5@tippex.mynet.homeunix.org>
Date: Wed, 6 Jan 2010 17:53:19 -0600
Message-ID: <51f3faa71001061553q29e0821evda63c4ca3eeee3b1@mail.gmail.com>
Subject: Re: Memory probing fails after 2.6.30 (bisected)
From: Robert Hancock <hancockrwd@gmail.com>
To: Anders Eriksson <aeriksson@fastmail.fm>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset=ISO-8859-1
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 861
Lines: 19

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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/