From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PULL v2 0/2] Qio next patches
Date: Thu, 28 Jun 2018 07:21:29 -0500 [thread overview]
Message-ID: <aeba92d8-8c8f-6d14-e12d-051ba2b2cfbe@redhat.com> (raw)
In-Reply-To: <20180628120821.10967-1-berrange@redhat.com>
On 06/28/2018 07:08 AM, Daniel P. Berrangé wrote:
> 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 10aef3e986b4ae3fd909308bdd41c4e7ee1d1d04:
>
> Delete AF_UNIX socket after close (2018-06-28 13:06:44 +0100)
>
> ----------------------------------------------------------------
> Merge qio 2018-06-28 v2
>
> Misc bug fixes for sockets channels
>
> ----------------------------------------------------------------
>
> Pavel Balaev (1):
> Delete AF_UNIX socket after close
>
> linzhecheng (1):
> socket: dont't free msgfds if error equals EAGAIN
Our mails crossed. Do you want a v3 that fixes the typo in the subject
line of 1/2?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2018-06-28 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 12:08 [Qemu-devel] [PULL v2 0/2] Qio next patches Daniel P. Berrangé
2018-06-28 12:08 ` [Qemu-devel] [PULL v2 1/2] socket: dont't free msgfds if error equals EAGAIN Daniel P. Berrangé
2018-06-28 12:08 ` [Qemu-devel] [PULL v2 2/2] Delete AF_UNIX socket after close Daniel P. Berrangé
2018-06-28 12:21 ` Eric Blake [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=aeba92d8-8c8f-6d14-e12d-051ba2b2cfbe@redhat.com \
--to=eblake@redhat.com \
--cc=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).