From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Paul Durrant <paul.durrant@citrix.com>, xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 0/4] docs: Document xenstore paths
Date: Wed, 11 Nov 2015 16:25:29 +0000 [thread overview]
Message-ID: <56436BF9.5020701@citrix.com> (raw)
In-Reply-To: <1447177241-20826-1-git-send-email-paul.durrant@citrix.com>
On 10/11/15 17:40, Paul Durrant wrote:
> Patch #1 documents paths, some already in used by XenServer, which can be
> used by guests to advertise contol capabilities.
>
> Patch #2 documents paths which can be used to advertise PV driver versions.
>
> Patch #3 documents paths which can be used by guests to advertise hotplug
> capabilities.
>
> Patch #4 documents paths which can be used by guests to advertise network
> addresses.
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
next prev parent reply other threads:[~2015-11-11 16:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 17:40 [PATCH v3 0/4] docs: Document xenstore paths Paul Durrant
2015-11-10 17:40 ` [PATCH v3 1/4] docs: Document control features the can be advertised by guests Paul Durrant
2015-11-10 17:40 ` [PATCH v3 2/4] docs: Document a xenstore path for PV driver version information Paul Durrant
2015-11-13 16:12 ` Ian Jackson
2015-11-13 16:17 ` Paul Durrant
2015-11-13 16:22 ` Ian Jackson
2015-11-10 17:40 ` [PATCH v3 3/4] docs: Document xenstore paths for domain hotplug features Paul Durrant
2015-11-10 17:40 ` [PATCH v3 4/4] docs: Document xenstore paths for domain network address information Paul Durrant
2015-11-13 16:18 ` Ian Jackson
2015-11-13 16:24 ` Paul Durrant
2015-11-13 16:34 ` Ian Jackson
2015-11-11 16:25 ` Andrew Cooper [this message]
2015-11-13 16:09 ` [PATCH v3 0/4] docs: Document xenstore paths Ian Jackson
2015-11-13 16:13 ` Paul Durrant
2015-11-13 16:20 ` Ian Jackson
2015-11-13 16:25 ` Paul Durrant
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=56436BF9.5020701@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=paul.durrant@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.