From: Ted Kaczmarek <tedkaz@optonline.net>
To: "Kamble, Nitin A" <nitin.a.kamble@intel.com>
Cc: Khoa Huynh <khoa@us.ibm.com>,
xen-devel-bounces@lists.xensource.com,
xen-devel <xen-devel@lists.xensource.com>,
"Li, Xin B" <xin.b.li@intel.com>,
Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Subject: RE: [PATCH] [VT] Fix for python breakge
Date: Fri, 21 Oct 2005 22:55:24 -0400 [thread overview]
Message-ID: <1129949724.4325.54.camel@pluto.linsolutions.com> (raw)
In-Reply-To: <E305A4AFB7947540BC487567B5449BA8084345C3@scsmsx402.amr.corp.intel.com>
On Fri, 2005-10-21 at 13:35 -0700, Kamble, Nitin A wrote:
> Xin's patch is making vcpus argument mandatory. This is not right. Xin
> can you fix your patch to make it optinal?
>
> Thanks & Regards,
> Nitin
> ------------------------------------------------------------------------
> -----------
> Open Source Technology Center, Intel Corp
>
> >-----Original Message-----
> >From: Khoa Huynh [mailto:khoa@us.ibm.com]
> >Sent: Friday, October 21, 2005 10:16 AM
> >To: Kamble, Nitin A
> >Cc: Keir Fraser; Ian Pratt; xen-devel; xen-devel-
> >bounces@lists.xensource.com; Li, Xin B
> >Subject: Re: [Xen-devel] [PATCH] [VT] Fix for python breakge
> >
> >I think this patch was included in a patch submitted by Xin Li a couple
> >days ago. I applied Li's patch and it fixed the problem for me.
> >Thanks.
> >
> >Regards,
> >
> >Khoa
> >
I posted something on this in my other post as well, optional is bad,
declaring everything may be a one time pain, but over the long haul it
is less problematic.
IMHO
Regards,
Ted
next prev parent reply other threads:[~2005-10-22 2:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 20:35 [PATCH] [VT] Fix for python breakge Kamble, Nitin A
2005-10-22 2:55 ` Ted Kaczmarek [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-21 23:19 Li, Xin B
2005-10-21 0:31 Kamble, Nitin A
2005-10-21 17:15 ` Khoa Huynh
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=1129949724.4325.54.camel@pluto.linsolutions.com \
--to=tedkaz@optonline.net \
--cc=khoa@us.ibm.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=nitin.a.kamble@intel.com \
--cc=xen-devel-bounces@lists.xensource.com \
--cc=xen-devel@lists.xensource.com \
--cc=xin.b.li@intel.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.