Message-ID: <495AC45D.8010102@kernel.org>
Date: Tue, 30 Dec 2008 17:01:17 -0800
From: "H. Peter Anvin" <hpa@kernel.org>
Organization: Linux Kernel Organization, Inc.
User-Agent: Thunderbird 2.0.0.14 (X11/20080501)
MIME-Version: 1.0
To: Frederic Weisbecker <fweisbec@gmail.com>
CC: Jaswinder Singh Rajput <jaswinder@infradead.org>,
       Ingo Molnar <mingo@elte.hu>, x86 maintainers <x86@kernel.org>,
       LKML <linux-kernel@vger.kernel.org>,
       Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH -tip] fix compilation error
References: <1230648007.10677.1.camel@jaswinder.satnam> <20081230205230.GA6151@nowhere> <495AA87D.9060704@kernel.org> <495ABDF8.2070703@kernel.org> <20081231004722.GA28472@nowhere>
In-Reply-To: <20081231004722.GA28472@nowhere>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1285
Lines: 31

Frederic Weisbecker wrote:
> On Tue, Dec 30, 2008 at 04:34:00PM -0800, H. Peter Anvin wrote:
>> H. Peter Anvin wrote:
>>> Applied to tip:tracing/kmemtrace2.
>>>
>> Hm, there still seems to be a build failure, in particular
>> trace_output.h is missing.  It looks to me at the moment as if just
>> removing the #include works; assuming that compiles I will check that in
>> to tip:tracing/kmemtrace2 as well.
>>
>> 	-hpa
> 
> While I worked on this tracer, I had to base the thing against tracing/kmemtrace
> because I needed the kmemtrace bits.
> But I saw that this topic was a bit out of sync against tip/master, some updates from
> Steven were not merged. But I didn't wonder, thinking that Ingo would resolve the
> conflicts. But it seems there were some lost stuffs :-)
> 
> I'm checking it and will send a patch to solve the rest...
> 

If it's only the trace_output.h #include removal, don't worry about it;
I'm about to commit that patch, but it would be good if you could check
out the tracing/kmemtrace2 branch afterwards.

	-hpa
--
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/