From: Michal Privoznik <mprivozn@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: imammedo@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [PATCH v2 0/2] qmp: Expose MachineClass::default_ram_id
Date: Tue, 28 Jul 2020 10:05:26 +0200 [thread overview]
Message-ID: <f820a890-da1f-9a0a-2484-6a1ffeafefb3@redhat.com> (raw)
In-Reply-To: <20200727184109.GB225270@habkost.net>
On 7/27/20 8:41 PM, Eduardo Habkost wrote:
> Hi Michal,
>
> It looks like this has fallen through the cracks, my apologies.
>
> I'm queueing this for 5.2. I assume this is the latest version,
> correct?
>
Yes. No worries, I forgot about it too :-) If I remembered, I would have
pinged.
Michal
prev parent reply other threads:[~2020-07-28 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 8:25 [PATCH v2 0/2] qmp: Expose MachineClass::default_ram_id Michal Privoznik
2020-05-26 8:25 ` [PATCH v2 1/2] qapi: Fix comment format for @CpuInstanceProperties Michal Privoznik
2020-05-26 13:11 ` Igor Mammedov
2020-05-26 8:25 ` [PATCH v2 2/2] qmp: Expose MachineClass::default_ram_id Michal Privoznik
2020-05-26 13:15 ` Igor Mammedov
2020-05-26 13:17 ` Igor Mammedov
2020-07-27 18:41 ` [PATCH v2 0/2] " Eduardo Habkost
2020-07-28 8:05 ` Michal Privoznik [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=f820a890-da1f-9a0a-2484-6a1ffeafefb3@redhat.com \
--to=mprivozn@redhat.com \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@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).