From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: "H. Peter Anvin" <hpa@kernel.org>,
Jaswinder Singh Rajput <jaswinder@infradead.org>,
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 09:14:58 +0100 [thread overview]
Message-ID: <20081231081458.GB12942@elte.hu> (raw)
In-Reply-To: <20081231014747.GB28472@nowhere>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> On Tue, Dec 30, 2008 at 05:01:17PM -0800, H. Peter Anvin wrote:
> > 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.
>
>
> Yes this topic builds well after your patch. So it was just this header.
Could you check whether latest tip/master is still OK? I had these
problems resolved locally (but forgot to push them out), and now i also
had to do a few conflict resolutions with latest -git, hopefully i have
not lost hpa's fixes ...
Ingo
next prev parent reply other threads:[~2008-12-31 8:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 14:40 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
2008-12-31 1:01 ` H. Peter Anvin
2008-12-31 1:47 ` Frederic Weisbecker
2008-12-31 8:14 ` Ingo Molnar [this message]
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=20081231081458.GB12942@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=hpa@kernel.org \
--cc=jaswinder@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®