From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Gerd Hoffmann" <kraxel@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: [Qemu-devel] [PULL v3 0/2] Qio next patches
Date: Thu, 28 Jun 2018 13:38:06 +0100 [thread overview]
Message-ID: <20180628123808.12165-1-berrange@redhat.com> (raw)
The following changes since commit 00928a421d47f49691cace1207481b7aad31b1f1:
Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20180626' into staging (2018-06-26 18:23:49 +0100)
are available in the Git repository at:
https://github.com/berrange/qemu tags/qio-next-pull-request
for you to fetch changes up to d66f78e1eaa832f73c771d9df1b606fe75d52a50:
Delete AF_UNIX socket after close (2018-06-28 13:36:59 +0100)
----------------------------------------------------------------
Merge qio 2018-06-28 v3
Misc bug fixes for sockets channels
----------------------------------------------------------------
Pavel Balaev (1):
Delete AF_UNIX socket after close
linzhecheng (1):
socket: don't free msgfds if error equals EAGAIN
chardev/char-socket.c | 4 ++--
io/channel-socket.c | 18 +++++++++++++++++-
2 files changed, 19 insertions(+), 3 deletions(-)
--
2.17.1
next reply other threads:[~2018-06-28 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 12:38 Daniel P. Berrangé [this message]
2018-06-28 12:38 ` [Qemu-devel] [PULL v3 1/2] socket: don't free msgfds if error equals EAGAIN Daniel P. Berrangé
2018-06-28 12:38 ` [Qemu-devel] [PULL v3 2/2] Delete AF_UNIX socket after close Daniel P. Berrangé
2018-06-29 8:03 ` [Qemu-devel] [PULL v3 0/2] Qio next patches Peter Maydell
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=20180628123808.12165-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).