From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
"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:44:20 +0100 [thread overview]
Message-ID: <20081231084420.GA13665@elte.hu> (raw)
In-Reply-To: <3f9a31f40812310040y27c39b87v456ae38e46031624@mail.gmail.com>
* Jaswinder Singh Rajput <jaswinderlinux@gmail.com> wrote:
> Hello Ingo,
>
> On Wed, Dec 31, 2008 at 1:44 PM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > 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 ...
> >
>
> With latest/tip, I am still getting error on X86_32 machines :
>
> CC mm/slab.o
> mm/slab.c:105:31: error: tracing/kmemtrace.h: No such file or directory
> make[1]: *** [mm/slab.o] Error 1
> make: *** [mm] Error 2
ok, pushed out a new one - does it build fine now?
Ingo
next prev parent reply other threads:[~2008-12-31 8:44 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
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 [this message]
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=20081231084420.GA13665@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=hpa@kernel.org \
--cc=jaswinder@infradead.org \
--cc=jaswinderlinux@gmail.com \
--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 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.