From: Zachary Amsden <zach@vmware.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Andi Kleen <ak@suse.de>, Rusty Russell <rusty@rustcorp.com.au>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Chris Wright <chrisw@sous-sol.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: PATCH: Fix VMI and COMPAT_VDSO for 2.6.21
Date: Sat, 10 Mar 2007 02:32:39 -0800 [thread overview]
Message-ID: <45F28947.30406@vmware.com> (raw)
In-Reply-To: <20070310084750.GA15647@elte.hu>
Ingo Molnar wrote:
> makes sense. We can do Jan's relocatable-COMPAT_VDSO thing in v2.6.22,
> but for v2.6.21 that's way too intrusive.
>
Agree. I think we can clean up some of the strange build magic though,
by adding boot time ELF magic instead. We'll see which works out better.
Zach
prev parent reply other threads:[~2007-03-10 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-10 7:00 PATCH: Fix VMI and COMPAT_VDSO for 2.6.21 Zachary Amsden
2007-03-10 7:01 ` Zachary Amsden
2007-03-10 8:47 ` Ingo Molnar
2007-03-10 10:32 ` Zachary Amsden [this message]
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=45F28947.30406@vmware.com \
--to=zach@vmware.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@osdl.org \
--cc=virtualization@lists.osdl.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;
as well as URLs for NNTP newsgroup(s).