From: Ian Campbell <ian.campbell@citrix.com>
To: Paul Durrant <paul.durrant@citrix.com>, xen-devel@lists.xenproject.org
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH v1 2/2] libxl: re-implement libxl__xs_printf()
Date: Wed, 2 Dec 2015 15:20:31 +0000 [thread overview]
Message-ID: <1449069631.4424.83.camel@citrix.com> (raw)
In-Reply-To: <1448978125-10724-3-git-send-email-paul.durrant@citrix.com>
On Tue, 2015-12-01 at 13:55 +0000, Paul Durrant wrote:
> This patch adds a new libxl__xs_vprintf() which actually checks the
> success of the underlying call to xs_write() (logging if it fails) and
> then re-implements libxl__xs_printf() using this (and replacing the
> call to vasprintf() with a call to libxl__vsprintf()).
Is the addition of libxl__xs_vprintf() an end in itself (i.e. do you have
an upcoming use for it) or just an artefact of how you decided to fix
libxl__xs_printf()?
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-12-02 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 13:55 [PATCH v1 0/2] libxl: change libxl__xs_write() to libxl__xs_printf() Paul Durrant
2015-12-01 13:55 ` [PATCH v1 1/2] libxl: re-name " Paul Durrant
2015-12-01 13:55 ` [PATCH v1 2/2] libxl: re-implement libxl__xs_printf() Paul Durrant
2015-12-02 15:20 ` Ian Campbell [this message]
2015-12-02 15:22 ` Paul Durrant
2015-12-08 17:04 ` Ian Campbell
2015-12-15 12:29 ` Ian Campbell
2015-12-15 12:30 ` Ian Campbell
2015-12-15 13:52 ` Paul Durrant
2015-12-15 15:13 ` Ian Campbell
-- strict thread matches above, loose matches on Subject: below --
2015-11-25 15:28 [PATCH v1 0/2] libxl: change libxl__xs_write() to libxl__xs_printf() Paul Durrant
2015-11-25 15:28 ` [PATCH v1 2/2] libxl: re-implement libxl__xs_printf() 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=1449069631.4424.83.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=paul.durrant@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@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.