From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, lukasstraub2@web.de
Subject: [PULL 0/7] Yank patches patches for 2021-01-13
Date: Wed, 13 Jan 2021 10:30:54 +0100 [thread overview]
Message-ID: <20210113093101.550964-1-armbru@redhat.com> (raw)
This pull request is on behalf of Lukas. Hope that's okay.
The following changes since commit f8e1d8852e393b3fd524fb005e38590063d99bc0:
Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20210112-1' into staging (2021-01-12 21:23:25 +0000)
are available in the Git repository at:
git://repo.or.cz/qemu/armbru.git tags/pull-yank-2021-01-13
for you to fetch changes up to 91d48e520a4a4f72e97aeb333029694f5d57cc93:
tests/test-char.c: Wait for the chardev to connect in char_socket_client_dupid_test (2021-01-13 10:21:17 +0100)
----------------------------------------------------------------
Yank patches patches for 2021-01-13
----------------------------------------------------------------
Lukas Straub (7):
Introduce yank feature
block/nbd.c: Add yank feature
chardev/char-socket.c: Add yank feature
migration: Add yank feature
io/channel-tls.c: make qio_channel_tls_shutdown thread-safe
io: Document qmp oob suitability of qio_channel_shutdown and io_shutdown
tests/test-char.c: Wait for the chardev to connect in char_socket_client_dupid_test
qapi/qapi-schema.json | 1 +
qapi/yank.json | 119 ++++++++++++++++++++++++
include/io/channel.h | 5 +-
include/qemu/yank.h | 97 ++++++++++++++++++++
block/nbd.c | 153 ++++++++++++++++++-------------
chardev/char-socket.c | 34 +++++++
io/channel-tls.c | 6 +-
migration/channel.c | 13 +++
migration/migration.c | 22 +++++
migration/multifd.c | 10 ++
migration/qemu-file-channel.c | 7 ++
migration/savevm.c | 5 +
tests/test-char.c | 1 +
util/yank.c | 207 ++++++++++++++++++++++++++++++++++++++++++
MAINTAINERS | 7 ++
qapi/meson.build | 1 +
util/meson.build | 1 +
17 files changed, 625 insertions(+), 64 deletions(-)
create mode 100644 qapi/yank.json
create mode 100644 include/qemu/yank.h
create mode 100644 util/yank.c
--
2.26.2
next reply other threads:[~2021-01-13 9:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 9:30 Markus Armbruster [this message]
2021-01-13 9:30 ` [PULL 1/7] Introduce yank feature Markus Armbruster
2021-01-13 9:30 ` [PULL 2/7] block/nbd.c: Add " Markus Armbruster
2021-01-13 9:30 ` [PULL 3/7] chardev/char-socket.c: " Markus Armbruster
2021-01-13 9:30 ` [PULL 4/7] migration: " Markus Armbruster
2021-01-13 9:30 ` [PULL 5/7] io/channel-tls.c: make qio_channel_tls_shutdown thread-safe Markus Armbruster
2021-01-13 9:31 ` [PULL 6/7] io: Document qmp oob suitability of qio_channel_shutdown and io_shutdown Markus Armbruster
2021-01-13 9:31 ` [PULL 7/7] tests/test-char.c: Wait for the chardev to connect in char_socket_client_dupid_test Markus Armbruster
2021-01-13 15:53 ` [PULL 0/7] Yank patches patches for 2021-01-13 Peter Maydell
2021-01-13 16:25 ` Markus Armbruster
2021-01-13 17:26 ` Lukas Straub
2021-01-14 11:02 ` Alex Bennée
2021-01-14 12:40 ` Markus Armbruster
2021-01-14 12:44 ` Lukas Straub
2021-01-14 13:19 ` [PATCH] Fix build with new yank feature by adding stubs Lukas Straub
2021-01-14 13:46 ` Alex Bennée
2021-01-14 14:04 ` Philippe Mathieu-Daudé
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=20210113093101.550964-1-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=lukasstraub2@web.de \
--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).