From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org, "Richard W.M. Jones" <rjones@redhat.com>
Subject: Re: [PULL 0/1] NBD patches for 2021-05-11
Date: Wed, 12 May 2021 05:42:18 +0200 [thread overview]
Message-ID: <af7caaf7-3067-9ebf-96f4-73e4a3dbc8d9@redhat.com> (raw)
In-Reply-To: <20210511192802.552706-1-eblake@redhat.com>
Hi Eric,
On 5/11/21 9:28 PM, Eric Blake wrote:
> The following changes since commit f9a576a818044133f8564e0d243ebd97df0b3280:
>
> Merge remote-tracking branch 'remotes/dgilbert-gitlab/tags/pull-virtiofs-20210506' into staging (2021-05-11 13:03:44 +0100)
>
> are available in the Git repository at:
>
> https://repo.or.cz/qemu/ericb.git tags/pull-nbd-2021-05-11
>
> for you to fetch changes up to 37179e9ea45d6428b29ae789209c119ac18c1d39:
>
> sockets: update SOCKET_ADDRESS_TYPE_FD listen(2) backlog (2021-05-11 12:43:26 -0500)
>
> ----------------------------------------------------------------
> nbd patches for 2021-05-11
>
> - fix fd passing to qemu-storage-daemon --nbd-server
>
> ----------------------------------------------------------------
> Stefan Hajnoczi (1):
> sockets: update SOCKET_ADDRESS_TYPE_FD listen(2) backlog
Richard suggested to add the following tag to the commit if possible:
"Resolves: https://gitlab.com/qemu-project/qemu/-/issues/218"
https://lists.gnu.org/archive/html/qemu-devel/2021-05/msg03107.html
next prev parent reply other threads:[~2021-05-12 3:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 19:28 [PULL 0/1] NBD patches for 2021-05-11 Eric Blake
2021-05-11 19:28 ` [PULL 1/1] sockets: update SOCKET_ADDRESS_TYPE_FD listen(2) backlog Eric Blake
2021-05-12 3:42 ` Philippe Mathieu-Daudé [this message]
2021-05-21 8:55 ` [PULL 0/1] NBD patches for 2021-05-11 Peter Maydell
2021-05-24 19:30 ` Eric Blake
2021-05-21 11:02 ` 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=af7caaf7-3067-9ebf-96f4-73e4a3dbc8d9@redhat.com \
--to=philmd@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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.