From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: konrad@darnok.org, Wei Liu <wei.liu2@citrix.com>,
Alexandra Sandulescu <alecsandra.sandulescu@gmail.com>,
xen-devel@lists.xenproject.org
Subject: Re: [OPW PATCH V4] tools: xl: refactor code to parse network device options
Date: Fri, 24 Oct 2014 13:17:25 -0400 [thread overview]
Message-ID: <20141024171725.GC12318@laptop.dumpdata.com> (raw)
In-Reply-To: <1414137663.3584.5.camel@citrix.com>
On Fri, Oct 24, 2014 at 09:01:03AM +0100, Ian Campbell wrote:
> On Thu, 2014-10-23 at 19:08 -0400, Konrad Rzeszutek Wilk wrote:
> > > He said the code *path*, not the code, IOW I would read that as "would
> > > be tested", NOT "has been tested".
> > >
> >
> > Aye. In which case let's wait for Alexandra's response to the testing
> > that Wei asked for.
>
> Alexandra replied to me (privately) a couple of days ago confirming that
> she has tested both code paths.
>
> > On a related note - one can setup OSSTest on ones own network, fairly easy right?
>
> Right in "standalone mode". It's far easier than it once was and we've
> been squashing speedbumps as new people try it.
>
> You do need some infrastructure such as PXE and dhcp and at least two
> machines (controller + test host). I think it would be overkill for a
> change of this magnitude (if that's what you were driving at).
Heck no. I just need to setup locally to supplement the automated testing
I do now.
>
> I think
> http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;h=9a85549cb600fa5be91bcbae6605f78616db63da;hb=2aa4fe7a4b138e5e88387af66f4fe14039a1f7ea is the best starting point for osstest, including standalone mode operation.
>
Thank you.
> Ian.
>
next prev parent reply other threads:[~2014-10-24 17:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 21:36 [OPW PATCH V4] tools: xl: refactor code to parse network device options Alexandra Sandulescu
2014-10-22 11:35 ` Ian Campbell
2014-10-22 20:21 ` Konrad Rzeszutek Wilk
2014-10-23 7:56 ` Ian Campbell
2014-10-23 20:08 ` Konrad Rzeszutek Wilk
2014-10-23 21:20 ` Ian Campbell
2014-10-23 23:08 ` Konrad Rzeszutek Wilk
2014-10-24 8:01 ` Ian Campbell
2014-10-24 8:58 ` Alexandra Sandulescu
2014-10-24 9:02 ` Ian Campbell
2014-10-24 9:12 ` Alexandra Sandulescu
2014-10-24 9:14 ` Ian Campbell
2014-10-24 9:17 ` Alexandra Sandulescu
2014-10-24 17:16 ` Konrad Rzeszutek Wilk
2014-10-24 17:17 ` Konrad Rzeszutek Wilk [this message]
2014-10-28 8:54 ` Alexandra Sandulescu
2014-10-24 9:32 ` Wei Liu
2015-01-12 17:58 ` Ian Campbell
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=20141024171725.GC12318@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=alecsandra.sandulescu@gmail.com \
--cc=konrad@darnok.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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.