From: Markus Armbruster <armbru@redhat.com>
To: Daniel Henrique Barboza <danielhb@linux.ibm.com>
Cc: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>,
mdroth@linux.vnet.ibm.com, qemu-devel@nongnu.org,
dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 0/2] qmp: 'wakeup-suspend-support' in query-target
Date: Tue, 15 May 2018 07:29:41 +0200 [thread overview]
Message-ID: <87vabplc56.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <ab7b28df-747b-0294-2c8f-2b7617a8915e@linux.ibm.com> (Daniel Henrique Barboza's message of "Mon, 14 May 2018 18:03:14 -0300")
Daniel Henrique Barboza <danielhb@linux.ibm.com> writes:
> On 05/14/2018 05:46 AM, Markus Armbruster wrote:
>> Markus Armbruster <armbru@redhat.com> writes:
>>
>>> Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com> writes:
>>>
>>>> Ping
>>> Michael, you reviewed v4 (at least in part), can you have a look?
>> Have these patches fallen through the cracks?
>>
> Should I re-send it? Not sure if this is applicable in the current
> code base anymore.
git-am isn't happy on current master. The conflicts look simple enough
for a maintainer to resolve, but that's yet another hurdle. Best to
respin, I think (assuming you still want the patches to go in).
next prev parent reply other threads:[~2018-05-15 5:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 14:12 [Qemu-devel] [PATCH v5 0/2] qmp: 'wakeup-suspend-support' in query-target Daniel Henrique Barboza
2018-02-19 14:12 ` [Qemu-devel] [PATCH v5 1/2] qmp: adding " Daniel Henrique Barboza
2018-02-19 14:12 ` [Qemu-devel] [PATCH v5 2/2] qga: update guest-suspend-ram and guest-suspend-hybrid descriptions Daniel Henrique Barboza
2018-03-14 13:12 ` [Qemu-devel] [PATCH v5 0/2] qmp: 'wakeup-suspend-support' in query-target Daniel Henrique Barboza
2018-04-13 14:05 ` Markus Armbruster
2018-05-14 8:46 ` Markus Armbruster
2018-05-14 21:03 ` Daniel Henrique Barboza
2018-05-15 5:29 ` Markus Armbruster [this message]
2018-05-15 14:22 ` Daniel Henrique Barboza
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=87vabplc56.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=danielhb@linux.ibm.com \
--cc=danielhb@linux.vnet.ibm.com \
--cc=dgilbert@redhat.com \
--cc=mdroth@linux.vnet.ibm.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 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.