[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 6 Jun 2008 10:33:22 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
the arch/x86 maintainers <x86@...nel.org>
Subject: Re: linux-next: Tree for June 5
* Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> On Fri, 6 Jun 2008 10:23:25 +0200 Ingo Molnar <mingo@...e.hu> wrote:
> >
> > hm, which commit is this exactly? I've never hit it myself in
> > bisection (and there are days when i bisect -tip several times).
> > We'll respin tip/tracing/mmiotrace if it's bisection-hostile. You
> > can probably nudge it into building via "git-bisect next".
>
> See my other email. This is because the ftrace tree does not merge
> well with the rcu tree.
yeah, we have this fixup in -tip as well, in a structured way: you might
want to start tracking the tip/tracing/mmiotrace-mergefixups branch to
pick it up.
or we could offer you a full auto-tip-next plug-and-play branch as well.
(there's no reason to redo all these integration steps)
Ingo
--
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