From: Ingo Molnar <mingo@elte.hu>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: compile problem in current x86.git
Date: Mon, 25 Feb 2008 21:50:35 +0100 [thread overview]
Message-ID: <20080225205035.GA3435@elte.hu> (raw)
In-Reply-To: <20080225204438.GA1213@elte.hu>
> > Hm. This is x86#testing, no? I don't think there's any kmemcheck
> > code whatsoever in other branches.
ah. that was x86.git#mm i think - a kmemcheck commit indeed prematurely
got into that branch.
I've updated x86.git and it should all have the correct ordering now.
(as of HEAD c9d2f5489cec70f814bf6)
Jeremy, you might want to start tracking x86.git#testing:
http://people.redhat.com/mingo/x86.git/README
if you want to follow the latest & greatest x86.git code.
Ingo
next prev parent reply other threads:[~2008-02-25 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 19:23 compile problem in current x86.git Jeremy Fitzhardinge
2008-02-25 20:37 ` Vegard Nossum
2008-02-25 20:44 ` Ingo Molnar
2008-02-25 20:50 ` Ingo Molnar [this message]
2008-02-26 0:17 ` Jeremy Fitzhardinge
2008-02-26 7:27 ` Ingo Molnar
2008-02-26 0:16 ` Jeremy Fitzhardinge
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=20080225205035.GA3435@elte.hu \
--to=mingo@elte.hu \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@gmail.com \
/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