From: Ian Campbell <Ian.Campbell@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Ian Jackson <ian.jackson@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH for 4.5] xl: Return proper error codes for block-attach and block-detach
Date: Tue, 25 Nov 2014 14:55:58 +0000 [thread overview]
Message-ID: <1416927358.32327.37.camel@citrix.com> (raw)
In-Reply-To: <CAFLBxZaLG8RGQ5Pce9TvczvJtg8t983X+stRNMD0VeYJgJ9VEw@mail.gmail.com>
On Thu, 2014-11-20 at 16:06 +0000, George Dunlap wrote:
> On Wed, Nov 12, 2014 at 5:31 PM, George Dunlap
> <george.dunlap@eu.citrix.com> wrote:
> > Return proper error codes on failure so that scripts can tell whether
> > the command completed properly or not.
>
> How about changing this to something like:
>
> ---
> Return proper error codes on failure so that scripts can tell whether
> the command completed properly or not.
>
> This is not a proper fix, since it fails to call
> libxl_device_disk_dispose() on the error path. But a proper fix
> requires some refactoring, so given where we are in the release
> process, it's better to have a fix that is simple and obvious, and do
> the refactoring once the next development window opens up.
>
> Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
Looks good, I kept the single line title the same and replaced the body
with the above, which I think is what you intended.
Konrad acked taking this patch for 4.5 in a reply to v2, so I have
pushed.
Ian.
prev parent reply other threads:[~2014-11-25 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 17:31 [PATCH for 4.5] xl: Return proper error codes for block-attach and block-detach George Dunlap
2014-11-12 17:35 ` Wei Liu
2014-11-13 8:16 ` Ian Campbell
2014-11-20 16:06 ` George Dunlap
2014-11-25 14:55 ` 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=1416927358.32327.37.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=ian.jackson@citrix.com \
--cc=wei.liu2@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 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.