From: George Dunlap <george.dunlap@eu.citrix.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: Ian Jackson <ian.jackson@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH 1/1] libxl: Use LOG_ERRNO rather than ERRNOVAL in libxl_pci.c
Date: Mon, 16 Sep 2013 14:34:33 +0100 [thread overview]
Message-ID: <523708E9.80701@eu.citrix.com> (raw)
In-Reply-To: <1379337775-10541-1-git-send-email-george.dunlap@eu.citrix.com>
On 16/09/13 14:22, George Dunlap wrote:
> The xc_* functions (now) return -1 on error and set errno.
>
> Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
> CC: Ian Jackson <ian.jackson@citrix.com>
> CC: Ian Campbell <ian.campbell@citrix.com>
Sorry, apparently '-n' in the context of 'git send-email' doesn't mean
"dry run", but instead, "use a number even if there is only one patch".
Both patches are the same, apply whichever one you please. :-)
-George
prev parent reply other threads:[~2013-09-16 13:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 13:22 [PATCH 1/1] libxl: Use LOG_ERRNO rather than ERRNOVAL in libxl_pci.c George Dunlap
2013-09-16 13:34 ` George Dunlap [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=523708E9.80701@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@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).