From: Olaf Hering <olaf@aepfle.de>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH 0/2] libxl: add support for pvscsi, iteration 13
Date: Mon, 20 Feb 2017 18:18:42 +0100 [thread overview]
Message-ID: <20170220181842.0c1b09f4.olaf@aepfle.de> (raw)
In-Reply-To: <20170220170518.amlghrpkkf4t2aiw@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 737 bytes --]
Am Mon, 20 Feb 2017 17:05:18 +0000
schrieb Wei Liu <wei.liu2@citrix.com>:
> CC Ian -- I think he followed more closely than I did.
Thanks, but this is just a rebase to 4.8 in case anyone needs it.
No code changes since last review round.
I'm currently working on an update for the idl representation to
support migration. 'pdev' has to be reevaluated on each dom0, which
means 'pdev' has to be a string and what is currently stored in a
"libxl_vscsi_pdev" has be evaluated shortly before it gets written to
xenstore. This avoids "libxl_vscsi_pdev_type" becoming part of the json.
Olaf
> > Changes between v12 and v13:
> > - rebase to 'staging' (936a7a5..a7a578ce6b)
> > - rebase to 'staging' (8b27d2b..936a7a5)
[-- Attachment #1.2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-02-20 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 10:49 [PATCH 0/2] libxl: add support for pvscsi, iteration 13 Olaf Hering
2017-02-17 10:49 ` [PATCH 1/2] libxl: add support for vscsi Olaf Hering
2017-02-17 10:49 ` [PATCH 2/2] Scripts to create and delete xen-scsiback nodes in Linux target framework Olaf Hering
2017-02-20 17:05 ` [PATCH 0/2] libxl: add support for pvscsi, iteration 13 Wei Liu
2017-02-20 17:18 ` Olaf Hering [this message]
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=20170220181842.0c1b09f4.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Jackson@eu.citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).