[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.00.0906202323580.2147@iabervon.org>
Date: Sun, 21 Jun 2009 00:08:05 -0400 (EDT)
From: Daniel Barkalow <barkalow@...ervon.org>
To: Frans Pop <elendil@...net.nl>
cc: Sean MacLennan <smaclennan@...atech.com>, linuxppc-dev@...abs.org,
linux-kernel@...r.kernel.org
Subject: Re: Badness on the Warp
On Sun, 21 Jun 2009, Frans Pop wrote:
> On Sunday 21 June 2009, Sean MacLennan wrote:
> > On Sat, 20 Jun 2009 22:56:45 +0200 Frans Pop <elendil@...net.nl> wrote:
> > > The fact that your bisect ended at a merge essentially means that it
> > > is invalid. As a merge does not introduce any actual change (unless
> > > it includes changes to resolve conflicts), it normally cannot be the
> > > cause of a regression.
> >
> > Makes sense I messed up somewhere. This is the commit that causes
> > problems:
> >
> > Merge branch 'topic/slab/earlyboot' of
> > git://git./linux/kernel/git/penberg/slab-2.6
> >
> > * 'topic/slab/earlyboot' of
> > git://git.kernel.org/pub/scm/linux/kernel/git/penberg/slab-2.6:
>
> Hmmm. That's b640f042faa2, which is another merge...
> So you're still not there.
It's not implausible that this is, in fact, the first bad commit. The
early slab topic could easily have been correct for everything in the tree
when it was written, but cause problems with some other patch developed
simultaneously.
It's worth rechecking that both 871fa90 and b8ec757 are good and
b640f042faa2 is bad, since it's also pretty likely that the test isn't
reproducing perfectly.
-Daniel
*This .sig left intentionally blank*
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists