From: Zachary Amsden <zach@vmware.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: vdso relocation
Date: Wed, 07 Mar 2007 13:59:21 -0800 [thread overview]
Message-ID: <45EF35B9.4050006@vmware.com> (raw)
In-Reply-To: <45EF1381.60501@goop.org>
Jeremy Fitzhardinge wrote:
> Are you working on cleaning up the patch? Do you think it will have any
> conflict with the Xen series?
>
> If all goes well, I'm planning on doing another patch post later today,
> and wondering if it can/should incorporate the vdso reloc changes, or if
> you can just post it as a separate change.
>
Probably leave out the vdso reloc changes for now ... they can always be
added back if somehow mine goes into the weeds, but I'm hopeful to have
a vdso relocation that works for all cases without the extra build
complexity.
Zach
prev parent reply other threads:[~2007-03-07 21:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 19:33 vdso relocation Jeremy Fitzhardinge
2007-03-07 21:59 ` 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=45EF35B9.4050006@vmware.com \
--to=zach@vmware.com \
--cc=jeremy@goop.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).