[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081002185509.GA32078@elte.hu>
Date: Thu, 2 Oct 2008 20:55:09 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Jonathan Corbet <corbet@....net>,
Mathieu Desnoyers <compudj@...stal.dyndns.org>,
LKML <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>,
prasad@...ux.vnet.ibm.com, "Frank Ch. Eigler" <fche@...hat.com>,
David Wilder <dwilder@...ibm.com>, hch@....de,
Martin Bligh <mbligh@...gle.com>,
Christoph Hellwig <hch@...radead.org>,
Masami Hiramatsu <mhiramat@...hat.com>,
Steven Rostedt <srostedt@...hat.com>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>
Subject: Re: [boot crash] Re: [PATCH] ring-buffer: fix build error
* Steven Rostedt <rostedt@...dmis.org> wrote:
>
> On Thu, 2 Oct 2008, Ingo Molnar wrote:
>
> >
> > * Steven Rostedt <rostedt@...dmis.org> wrote:
> >
> > >
> > > On Thu, 2 Oct 2008, Ingo Molnar wrote:
> > > > * Ingo Molnar <mingo@...e.hu> wrote:
> > >
> > > > full serial log and config attached. I'm excluding these latest commits
> > >
> > > -ENOATTACHMENT
> >
> > attached.
> >
> > You can get the broken tree by doing this in tip/master:
> >
> > git-merge tip/tracing/ring-buffer
>
> I've just checked-out tip/tracing/ring-buffer. That tree is still broken
> too, right? Or do I need to merge it to get the broken version?
yes, that's very likely broken too in a standalone way as well - but to
get the exact tree i tested i'd suggest:
git checkout tip/master
git merge tip/tracing/ring-buffer
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