From: Ian Campbell <ian.campbell@citrix.com>
To: "Pang, LongtaoX" <longtaox.pang@intel.com>
Cc: "wei.liu2@citrix.com" <wei.liu2@citrix.com>,
"Hu, Robert" <robert.hu@intel.com>,
"Ian.Jackson@eu.citrix.com" <Ian.Jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [OSSTEST Nested PATCH v7 2/6] Edit some testsupport APIs for nested test
Date: Wed, 1 Apr 2015 09:50:54 +0100 [thread overview]
Message-ID: <1427878254.2115.225.camel@citrix.com> (raw)
In-Reply-To: <86C3224E41A7434B904EC364302132D80E487BFD@SHSMSX101.ccr.corp.intel.com>
On Wed, 2015-04-01 at 05:56 +0000, Pang, LongtaoX wrote:
>
>
> > -----Original Message-----
> > From: Ian Campbell [mailto:ian.campbell@citrix.com]
> > Sent: Tuesday, March 31, 2015 9:50 PM
> > To: Pang, LongtaoX
> > Cc: xen-devel@lists.xen.org; Ian.Jackson@eu.citrix.com; wei.liu2@citrix.com;
> > Hu, Robert
> > Subject: Re: [OSSTEST Nested PATCH v7 2/6] Edit some testsupport APIs for
> > nested test
> >
> > On Fri, 2015-03-27 at 19:06 -0400, longtao.pang wrote:
> > > 1. Designate vif model to 'e1000' by make-flight.
> >
> > Strictly you could s/to 'e1000'// here since the make-flight changes are
> > elsewhere and that would better describe the generic change.
> >
> Do you mean that I should change the description from "Designate vif
> model to 'e1000' by make-flight" to "Designate vif model by
> make-flight"?
Yes, or even better "Add runvar to allow override of default VIF model".
> > > 2. In L2 installation context, its host (L1) IP address is not queried
> > > from DNS, but after running "ts-nested-setup + host + nested", L1 IP
> > > is stored in runvar.
> > >
> > > Signed-off-by: longtao.pang <longtaox.pang@intel.com>
> >
> > Acked-by: Ian Campbell <ian.campbell@citrix.com>
> >
>
next prev parent reply other threads:[~2015-04-01 8:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 23:06 [OSSTEST Nested PATCH v7 0/6] Introduction of netsted HVM test job longtao.pang
2015-03-27 23:06 ` [OSSTEST Nested PATCH v7 1/6] parsing grub which has 'submenu' primitive longtao.pang
2015-03-31 13:44 ` Ian Campbell
2015-04-01 1:42 ` Hu, Robert
2015-03-27 23:06 ` [OSSTEST Nested PATCH v7 2/6] Edit some testsupport APIs for nested test longtao.pang
2015-03-31 13:49 ` Ian Campbell
2015-04-01 5:56 ` Pang, LongtaoX
2015-04-01 8:50 ` Ian Campbell [this message]
2015-03-31 14:20 ` Ian Campbell
2015-03-27 23:06 ` [OSSTEST Nested PATCH v7 3/6] Changes on test step of debain hvm guest install longtao.pang
2015-03-31 13:55 ` Ian Campbell
2015-04-01 8:19 ` Pang, LongtaoX
2015-04-01 8:53 ` Ian Campbell
2015-03-27 23:06 ` [OSSTEST Nested PATCH v7 4/6] Add new script to custmize nested test configuration longtao.pang
2015-03-31 14:13 ` Ian Campbell
2015-04-01 8:45 ` Pang, LongtaoX
2015-04-01 8:58 ` Ian Campbell
2015-04-09 7:12 ` Pang, LongtaoX
2015-04-15 9:31 ` Ian Campbell
2015-03-27 23:06 ` [OSSTEST Nested PATCH v7 5/6] Add test job for nest test case longtao.pang
2015-03-31 14:23 ` Ian Campbell
2015-04-01 8:27 ` Pang, LongtaoX
2015-04-01 9:06 ` Ian Campbell
2015-04-02 8:16 ` Pang, LongtaoX
2015-04-02 9:15 ` Ian Campbell
2015-03-27 23:06 ` [OSSTEST Nested PATCH v7 6/6] Compose the main recipe of nested test job longtao.pang
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=1427878254.2115.225.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=longtaox.pang@intel.com \
--cc=robert.hu@intel.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 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.