All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Paul Durrant <paul.durrant@citrix.com>, xen-devel@lists.xenproject.org
Subject: Re: [PATCH v5 0/4] docs: Document xenstore paths
Date: Tue, 24 Nov 2015 16:53:04 +0000	[thread overview]
Message-ID: <1448383984.26412.65.camel@citrix.com> (raw)
In-Reply-To: <1447759925-4441-1-git-send-email-paul.durrant@citrix.com>

On Tue, 2015-11-17 at 11:32 +0000, Paul Durrant wrote:

All applied with Ian's acks.

> 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.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

      parent reply	other threads:[~2015-11-24 16:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17 11:32 [PATCH v5 0/4] docs: Document xenstore paths Paul Durrant
2015-11-17 11:32 ` [PATCH v5 1/4] docs: Introduce xenstore paths for PV control features Paul Durrant
2015-11-17 11:32 ` [PATCH v5 2/4] docs: Introduce xenstore paths for PV driver information Paul Durrant
2015-11-23 11:31   ` Ian Jackson
2015-11-17 11:32 ` [PATCH v5 3/4] docs: Introduce xenstore paths for hotplug features Paul Durrant
2015-11-23 11:32   ` Ian Jackson
2015-11-17 11:32 ` [PATCH v5 4/4] docs: Introduce xenstore paths for guest network address information Paul Durrant
2015-11-18 12:00   ` Olaf Hering
2015-11-18 12:04     ` Paul Durrant
2015-11-18 12:05     ` Andrew Cooper
2015-11-23 11:32   ` Ian Jackson
2015-11-24 16:53 ` Ian Campbell [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=1448383984.26412.65.camel@citrix.com \
    --to=ian.campbell@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.