qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
	qemu-devel@nongnu.org, Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH stable-1.4 0/4] monitor: do not rely on O_NONBLOCK for passed file descriptors
Date: Thu, 04 Apr 2013 06:25:18 -0600	[thread overview]
Message-ID: <515D712E.4090605@redhat.com> (raw)
In-Reply-To: <1365075615-14027-1-git-send-email-stefanha@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]

On 04/04/2013 05:40 AM, Stefan Hajnoczi wrote:
> Backported to QEMU 1.4 stable branch.
> 
> Original series:
> http://lists.nongnu.org/archive/html/qemu-devel/2013-03/msg04756.html
> 
> Stefan Hajnoczi (4):
>   oslib-posix: rename socket_set_nonblock() to qemu_set_nonblock()
>   net: ensure "socket" backend uses non-blocking fds
>   qemu-socket: set passed fd non-blocking in socket_connect()
>   chardev: clear O_NONBLOCK on SCM_RIGHTS file descriptors
> 
>  block/nbd.c            |  2 +-
>  block/sheepdog.c       |  6 +++---
>  include/qemu/sockets.h |  4 ++--
>  migration-tcp.c        |  2 +-
>  migration-unix.c       |  2 +-
>  migration.c            |  2 +-
>  nbd.c                  |  8 ++++----
>  net/socket.c           | 13 +++++++++----
>  qemu-char.c            | 11 +++++++----
>  slirp/misc.c           |  2 +-
>  slirp/tcp_subr.c       |  4 ++--
>  ui/vnc.c               |  2 +-
>  util/oslib-posix.c     |  4 ++--
>  util/oslib-win32.c     |  4 ++--
>  util/qemu-sockets.c    |  5 +++--
>  15 files changed, 40 insertions(+), 31 deletions(-)

Series: Reviewed-by: Eric Blake <eblake@redhat.com>

Is it worth including cherry-pick ids and descriptions of the conflict
resolution done during the backport?

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]

  parent reply	other threads:[~2013-04-04 12:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 11:40 [Qemu-devel] [PATCH stable-1.4 0/4] monitor: do not rely on O_NONBLOCK for passed file descriptors Stefan Hajnoczi
2013-04-04 11:40 ` [Qemu-devel] [PATCH stable-1.4 1/4] oslib-posix: rename socket_set_nonblock() to qemu_set_nonblock() Stefan Hajnoczi
2013-04-04 11:40 ` [Qemu-devel] [PATCH stable-1.4 2/4] net: ensure "socket" backend uses non-blocking fds Stefan Hajnoczi
2013-04-04 11:40 ` [Qemu-devel] [PATCH stable-1.4 3/4] qemu-socket: set passed fd non-blocking in socket_connect() Stefan Hajnoczi
2013-04-04 11:40 ` [Qemu-devel] [PATCH stable-1.4 4/4] chardev: clear O_NONBLOCK on SCM_RIGHTS file descriptors Stefan Hajnoczi
2013-04-04 12:25 ` Eric Blake [this message]
2013-04-04 13:27   ` [Qemu-devel] [PATCH stable-1.4 0/4] monitor: do not rely on O_NONBLOCK for passed " Markus Armbruster
2013-04-04 13:56 ` Stefan Hajnoczi

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=515D712E.4090605@redhat.com \
    --to=eblake@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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 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).