From: Paul Durrant <paul.durrant@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Paul Durrant <paul.durrant@citrix.com>
Subject: [PATCH v2 0/3] libxl: xenstore related cleanup
Date: Mon, 16 Nov 2015 14:00:20 +0000 [thread overview]
Message-ID: <1447682423-1638-1-git-send-email-paul.durrant@citrix.com> (raw)
This series is v2 since patches #1 and #3 were part of my previous
RFC posting.
Patch #1 is a cosmetic change to re-name a function so that the name of
a function introduced in a subsequent patch makes more sense
Patch #2 passes back errors from libx__xs_printf() and
libxl__xs_writev_perms() if the underlying xenstore operations fail
Patch #3 stops mis-use of XS_MKDIR
next reply other threads:[~2015-11-16 14:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 14:00 Paul Durrant [this message]
2015-11-16 14:00 ` [PATCH v2 1/3] libxl: re-name libxl__xs_write() to libxl__xs_printf() Paul Durrant
2015-11-16 17:15 ` Ian Jackson
2015-11-24 16:22 ` Ian Campbell
2015-11-25 11:27 ` Paul Durrant
2015-11-16 14:00 ` [PATCH v2 2/3] libxl: check for underlying xenstore operation failure Paul Durrant
2015-11-24 16:48 ` Ian Jackson
2015-11-24 17:24 ` Paul Durrant
2015-11-16 14:00 ` [PATCH v2 3/3] libxl: stop using libxl__xs_mkdir() for ~/control/shutdown 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=1447682423-1638-1-git-send-email-paul.durrant@citrix.com \
--to=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.