All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: "Hu, Robert" <robert.hu@intel.com>
Cc: xen-devel@lists.xenproject.org,
	Ian Campbell <ian.campbell@citrix.com>,
	"Jin, Gordon" <gordon.jin@intel.com>
Subject: Osstest nested patch v15 (was RE: [OSSTEST PATCH v14 PART 2 10-26/26] Nested HVM testing)
Date: Tue, 10 Nov 2015 19:46:06 +0000	[thread overview]
Message-ID: <22082.18814.474689.243994@mariner.uk.xensource.com> (raw)
In-Reply-To: <9E79D1C9A97CFD4097BCE431828FDD3102346249@SHSMSX103.ccr.corp.intel.com>

Hu, Robert writes ("Osstest nested patch v15 (was RE: [OSSTEST PATCH v14 PART 2 10-26/26] Nested HVM testing)"):
> I here hand over to you the v15 patch bundle as attached. Hope it can pass your pretest soon.

Thanks.  (CCing the list.)

All of your fixes were good.  Thank you.  I have incorporated them.

> * The last patch of 'guest' Serial method, was made by myself, you
> may want to rewrite it or modify it. I don't have the
> confidence. But it doesn't blocks others, with or without it, the
> patch set can work fine.

I rewrote this.  I found I wanted to do some refactoring first to make
this easier.

I am going to send out a v16 of the whole series in just a moment.

Can you please test this final patch in your environment ?  Send me
fixes in whatever form you like.

I think we do need this debug keys feature to work before we push this
to osstest pretest, because otherwise we risk having un-debuggable
blocking failures in our CI.

Regards,
Ian.

       reply	other threads:[~2015-11-10 19:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9E79D1C9A97CFD4097BCE431828FDD3102346249@SHSMSX103.ccr.corp.intel.com>
2015-11-10 19:46 ` Ian Jackson [this message]
2015-11-11  5:23   ` Osstest nested patch v15 (was RE: [OSSTEST PATCH v14 PART 2 10-26/26] Nested HVM testing) Hu, Robert
2015-11-11  9:35     ` Ian Jackson
2015-11-11 10:15       ` Hu, Robert
2015-11-11 11:08         ` Ian Jackson
2015-11-11 14:05           ` Ian Jackson
2015-11-11 17:00             ` Ian Jackson
2015-11-12  5:43             ` Hu, Robert
2015-11-12 16:10               ` Ian Jackson
2015-11-13  1:53                 ` Hu, Robert
2015-11-13 10:29                   ` Ian Jackson
2015-11-16  1:49                     ` Hu, Robert
2015-11-16 10:30                       ` Ian Campbell
2015-11-16 10:39                         ` Hu, Robert
2015-11-16 15:20                           ` Ian Jackson
2015-11-16 15:20                         ` Ian Jackson
2015-11-16 15:20                           ` [OSSTEST PATCH 1/2] Nested hosts: Provide hostnamepath and hostnamepath_list Ian Jackson
2015-11-16 15:20                             ` [OSSTEST PATCH 2/2] Nested hosts: Use hostnamepath() in create_webfile Ian Jackson
2015-11-16 15:37                               ` Ian Campbell
2015-11-16 15:37                             ` [OSSTEST PATCH 1/2] Nested hosts: Provide hostnamepath and hostnamepath_list Ian Campbell
2015-11-17  2:14                             ` Hu, Robert
2015-11-17  9:51                               ` Ian Campbell
2015-11-17 10:32                                 ` Hu, Robert

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=22082.18814.474689.243994@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=gordon.jin@intel.com \
    --cc=ian.campbell@citrix.com \
    --cc=robert.hu@intel.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.