From: Thomas Huth <thuth@redhat.com>
To: Lukas Straub <lukasstraub2@web.de>, qemu-devel <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Alex Bennee <alex.bennee@linaro.org>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH 1/2] yank: Remove dependency on qiochannel
Date: Tue, 23 Mar 2021 19:03:49 +0100 [thread overview]
Message-ID: <7b9cc130-7e9d-238c-7fa1-6dda216444e2@redhat.com> (raw)
In-Reply-To: <20ff143fc2db23e27cd41d38043e481376c9cec1.1616521341.git.lukasstraub2@web.de>
On 23/03/2021 18.52, Lukas Straub wrote:
> Remove dependency on qiochannel by removing yank_generic_iochannel and
> letting migration and chardev use their own yank function for
> iochannel.
>
> Signed-off-by: Lukas Straub <lukasstraub2@web.de>
> ---
> MAINTAINERS | 1 +
> chardev/char-socket.c | 21 ++++++++++++++-------
> include/qemu/yank.h | 10 ----------
> migration/channel.c | 6 ++++--
> migration/meson.build | 1 +
> migration/multifd.c | 3 ++-
> migration/qemu-file-channel.c | 3 ++-
> migration/yank_functions.c | 20 ++++++++++++++++++++
> migration/yank_functions.h | 17 +++++++++++++++++
> stubs/yank.c | 6 ------
> util/yank.c | 8 --------
> 11 files changed, 61 insertions(+), 35 deletions(-)
> create mode 100644 migration/yank_functions.c
> create mode 100644 migration/yank_functions.h
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2021-03-23 18:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 17:52 [PATCH 0/2] yank: Always link full yank code Lukas Straub
2021-03-23 17:52 ` [PATCH 1/2] yank: Remove dependency on qiochannel Lukas Straub
2021-03-23 18:03 ` Thomas Huth [this message]
2021-03-25 20:29 ` Marc-André Lureau
2021-03-23 17:52 ` [PATCH 2/2] yank: Always link full yank code Lukas Straub
2021-03-23 18:04 ` Thomas Huth
2021-03-25 20:30 ` Marc-André Lureau
2021-03-23 19:09 ` [PATCH 0/2] " Daniel P. Berrangé
2021-03-24 11:22 ` Lukas Straub
2021-03-24 11:36 ` Daniel P. Berrangé
2021-03-24 12:09 ` Lukas Straub
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=7b9cc130-7e9d-238c-7fa1-6dda216444e2@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=lukasstraub2@web.de \
--cc=pbonzini@redhat.com \
--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).