From: Kip Macy <kip.macy@gmail.com>
To: Christian.Limpach@cl.cam.ac.uk
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
Mike Wray <mike.wray@hp.com>, Ryan Harper <ryanh@us.ibm.com>,
xen-devel@lists.xensource.com
Subject: Re: [RESUBMIT] [PATCH] xen, tools: pincpu use vcpu and cpumap_t
Date: Wed, 11 May 2005 14:18:48 -0700 [thread overview]
Message-ID: <b1fa29170505111418386542ba@mail.gmail.com> (raw)
In-Reply-To: <3d8eece2050511141728ab10e8@mail.gmail.com>
Great, I really appreciate it.
-Kip
On 5/11/05, Christian Limpach <christian.limpach@gmail.com> wrote:
> On 5/11/05, Kip Macy <kip.macy@gmail.com> wrote:
> > Yes, this patch obviously conflicts with mine. The GETVCPUCONTEXT
> > patch has not gone in yet, nor have I received feedback. Should I
> > resolve the conflicts and re-submit?
>
> I've also applied your patch and resolved some of the conflicts. I've
> pushed the Changesets out to bkbits now. What remains to be done is
> to move the two arrays in getdomaininfo to getvcpucontext to get rid
> of the fixed size arrays.
>
> christian
>
next prev parent reply other threads:[~2005-05-11 21:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 22:31 [PATCH] xen,tools: pincpu use vcpu and cpumap_t Ryan Harper
2005-04-26 23:14 ` Lars Rasmusson
2005-05-03 16:51 ` Mike Wray
2005-05-03 23:58 ` [RESUBMIT] [PATCH] xen, tools: " Ryan Harper
2005-05-05 15:49 ` Mike Wray
2005-05-10 13:59 ` Mike Wray
2005-05-10 14:59 ` Ryan Harper
2005-05-10 15:55 ` Ryan Harper
2005-05-11 15:16 ` Mike Wray
2005-05-11 20:30 ` Christian Limpach
2005-05-11 20:41 ` Kip Macy
2005-05-11 21:17 ` Christian Limpach
2005-05-11 21:18 ` Kip Macy [this message]
2005-05-12 15:16 ` Mike Wray
2005-05-12 16:06 ` Mike Wray
2005-05-12 16:17 ` Ryan Harper
-- strict thread matches above, loose matches on Subject: below --
2005-05-11 21:09 Ian Pratt
2005-05-11 21:17 ` Kip Macy
2005-05-13 15:20 ` Mike Wray
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=b1fa29170505111418386542ba@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=mike.wray@hp.com \
--cc=ryanh@us.ibm.com \
--cc=xen-devel@lists.xensource.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 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.