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:44:38 +0100 [thread overview]
Message-ID: <20080225204438.GA1213@elte.hu> (raw)
In-Reply-To: <19f34abd0802251237q2aa5db03s522c77340cdc96a@mail.gmail.com>
* Vegard Nossum <vegard.nossum@gmail.com> wrote:
> > asm-x86/kmemcheck.h does seem to be completely missing. Looks like
> > 8db0acefb3025795abe3f37669354677a03de680 "x86: add hooks for
> > kmemcheck" should have added the file.
>
> Hm. This is x86#testing, no? I don't think there's any kmemcheck code
> whatsoever in other branches.
>
> The file should be added with this commit:
>
> kmemcheck: add the kmemcheck core
> http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-x86.git;a=commit;h=c83d05d69382945c92a2e7a2b168c1cc2aa77c29
yes, x86.git looks fine here too:
~/linux.trees.git> git-checkout -b tmp x86/testing
Branch tmp set up to track remote branch refs/remotes/x86/testing.
Switched to a new branch "tmp"
~/linux.trees.git> cd include/asm-x86/
~/linux.trees.git/include/asm-x86> ls -l kmemcheck.h
-rw-rw-r-- 1 mingo mingo 55 2008-02-25 21:41 kmemcheck.h
~/linux.trees.git/include/asm-x86> cd ..
~/linux.trees.git/include> cd ..
~/linux.trees.git> ls -ldt include/asm-x86/kmemcheck.h
-rw-rw-r-- 1 mingo mingo 55 2008-02-25 21:41 include/asm-x86/kmemcheck.h
~/linux.trees.git> git-log | head -1
commit c9d2f5489cec70f814bf64033290e5f05b4d7f33
Ingo
next prev parent reply other threads:[~2008-02-25 20:45 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 [this message]
2008-02-25 20:50 ` Ingo Molnar
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=20080225204438.GA1213@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