From: Frederic Weisbecker <fweisbec@gmail.com>
To: "H. Peter Anvin" <hpa@kernel.org>
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
Date: Wed, 31 Dec 2008 01:47:23 +0100 [thread overview]
Message-ID: <20081231004722.GA28472@nowhere> (raw)
In-Reply-To: <495ABDF8.2070703@kernel.org>
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...
next prev parent reply other threads:[~2008-12-31 0:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 14:40 [PATCH -tip] fix compilation error Jaswinder Singh Rajput
2008-12-30 20:52 ` Frederic Weisbecker
2008-12-30 23:02 ` H. Peter Anvin
2008-12-31 0:34 ` H. Peter Anvin
2008-12-31 0:47 ` Frederic Weisbecker [this message]
2008-12-31 1:01 ` H. Peter Anvin
2008-12-31 1:47 ` Frederic Weisbecker
2008-12-31 8:14 ` Ingo Molnar
2008-12-31 8:40 ` Jaswinder Singh Rajput
2008-12-31 8:44 ` Ingo Molnar
2008-12-31 9:45 ` Jaswinder Singh Rajput
2008-12-31 14:12 ` Frederic Weisbecker
2009-01-02 21:52 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081231004722.GA28472@nowhere \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@kernel.org \
--cc=jaswinder@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.