All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] block/ssh: Avoid segfault if inet_connect doesn't set errno.
Date: Tue, 28 Jul 2015 00:24:27 -0400	[thread overview]
Message-ID: <20150728042427.GJ21772@localhost.localdomain> (raw)
In-Reply-To: <1437571667-1093-1-git-send-email-rjones@redhat.com>

On Wed, Jul 22, 2015 at 02:27:46PM +0100, Richard W.M. Jones wrote:
> v3:
> Same as v2 but set the return value to -EIO.
>

Thanks, applied to my block tree:

https://github.com/codyprime/qemu-kvm-jtc/tree/block

Thanks,
Jeff

      parent reply	other threads:[~2015-07-28  4:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22 13:27 [Qemu-devel] [PATCH v3] block/ssh: Avoid segfault if inet_connect doesn't set errno Richard W.M. Jones
2015-07-22 13:27 ` Richard W.M. Jones
2015-07-22 13:56   ` Jeff Cody
2015-07-24 15:08     ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-07-24 15:14       ` Jeff Cody
2015-07-28  4:24 ` Jeff Cody [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=20150728042427.GJ21772@localhost.localdomain \
    --to=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.com \
    /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.