From: Markus Armbruster <armbru@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Eric Blake" <eblake@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Lukas Straub" <lukasstraub2@web.de>,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-block <qemu-block@nongnu.org>,
"Juan Quintela" <quintela@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Max Reitz" <mreitz@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH v11 0/7] Introduce 'yank' oob qmp command to recover from hanging qemu
Date: Tue, 01 Dec 2020 17:34:55 +0100 [thread overview]
Message-ID: <87pn3tpjrk.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <cover.1605439674.git.lukasstraub2@web.de> (Lukas Straub's message of "Sun, 15 Nov 2020 12:35:41 +0100")
Lukas Straub <lukasstraub2@web.de> writes:
> Hello Everyone,
> So here is v11.
> @Eric Blake and @Marc-André Lureau: We still need ACKs for NBD and chardev.
Once we have them, I can take the series through my tree.
prev parent reply other threads:[~2020-12-01 16:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 11:35 [PATCH v11 0/7] Introduce 'yank' oob qmp command to recover from hanging qemu Lukas Straub
2020-11-15 11:36 ` [PATCH v11 1/7] Introduce yank feature Lukas Straub
2020-12-01 20:43 ` Eric Blake
2020-12-01 21:05 ` Eric Blake
2020-11-15 11:36 ` [PATCH v11 2/7] block/nbd.c: Add " Lukas Straub
2020-12-01 20:50 ` Eric Blake
2020-12-02 12:18 ` Vladimir Sementsov-Ogievskiy
2020-12-02 12:34 ` Lukas Straub
2020-11-15 11:36 ` [PATCH v11 3/7] chardev/char-socket.c: " Lukas Straub
2020-11-15 11:36 ` [PATCH v11 4/7] migration: " Lukas Straub
2020-11-15 11:36 ` [PATCH v11 5/7] io/channel-tls.c: make qio_channel_tls_shutdown thread-safe Lukas Straub
2020-11-15 11:36 ` [PATCH v11 6/7] io: Document qmp oob suitability of qio_channel_shutdown and io_shutdown Lukas Straub
2020-11-15 11:36 ` [PATCH v11 7/7] tests/test-char.c: Wait for the chardev to connect in char_socket_client_dupid_test Lukas Straub
2020-12-01 16:34 ` Markus Armbruster [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=87pn3tpjrk.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=lukasstraub2@web.de \
--cc=marcandre.lureau@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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.