From: Markus Armbruster <armbru@redhat.com>
To: Li Zhang <li.zhang@ionos.com>
Cc: Lukas Straub <lukasstraub2@web.de>,
alexandr.iarygin@profitbricks.com, QEMU <qemu-devel@nongnu.org>,
Li Zhang <li.zhang@cloud.ionos.com>,
Pankaj Gupta <pankaj.gupta@cloud.ionos.com>,
Li Zhang <zhlcindy@gmail.com>,
marcandre.lureau@redhat.com
Subject: Re: [PATCH 2/2] Support monitor chardev hotswap with QMP
Date: Fri, 26 Mar 2021 15:40:00 +0100 [thread overview]
Message-ID: <874kgykmgv.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAEM4iGG67hQDPVrKbSsSpsrpbc12+ky=ROh26QUqO5C0+q0jXg@mail.gmail.com> (Li Zhang's message of "Tue, 23 Mar 2021 14:14:52 +0100")
Li Zhang <li.zhang@ionos.com> writes:
> Hi,
>
> Any comments about this patch?
I wanted to review this before my Easter break, but I'm out of time :(
When I'm back (April 6), I'll check whether it still needs review, but I
do hope somebody else can look at it sooner.
next prev parent reply other threads:[~2021-03-26 14:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 17:06 [PATCH 1/2] Fix the segment fault when calling yank_register_instance Li Zhang
2021-03-15 17:06 ` [PATCH 2/2] Support monitor chardev hotswap with QMP Li Zhang
2021-03-23 13:14 ` Li Zhang
2021-03-26 14:40 ` Markus Armbruster [this message]
2021-03-26 15:19 ` Li Zhang
2021-04-12 12:41 ` Li Zhang
2021-04-12 13:10 ` Markus Armbruster
2021-04-12 13:41 ` Li Zhang
2021-04-12 14:19 ` Pankaj Gupta
2021-04-13 6:40 ` Markus Armbruster
2021-04-13 8:51 ` Li Zhang
2021-04-16 9:33 ` Markus Armbruster
2021-04-16 9:52 ` Li Zhang
2021-04-13 8:57 ` Daniel P. Berrangé
2021-04-13 9:33 ` Li Zhang
2021-03-15 18:51 ` [PATCH 1/2] Fix the segment fault when calling yank_register_instance Marc-André Lureau
2021-03-16 9:45 ` Li Zhang
2021-03-16 14:46 ` Li Zhang
2021-03-16 15:24 ` Marc-André Lureau
2021-03-16 15:36 ` Li Zhang
2021-03-17 21:06 ` Lukas Straub
2021-03-26 14:41 ` Markus Armbruster
2021-03-26 16:02 ` Lukas Straub
2021-03-26 16:13 ` Markus Armbruster
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=874kgykmgv.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=alexandr.iarygin@profitbricks.com \
--cc=li.zhang@cloud.ionos.com \
--cc=li.zhang@ionos.com \
--cc=lukasstraub2@web.de \
--cc=marcandre.lureau@redhat.com \
--cc=pankaj.gupta@cloud.ionos.com \
--cc=qemu-devel@nongnu.org \
--cc=zhlcindy@gmail.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.