From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: David Hildenbrand <david@redhat.com>,
qemu-devel@nongnu.org, David Gibson <david@gibson.dropbear.id.au>,
Igor Mammedov <imammedo@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 0/2] range/memory-device: fixes and cleanups
Date: Mon, 17 Dec 2018 18:08:19 -0500 [thread overview]
Message-ID: <20181217180801-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20181217230624.GM7141@habkost.net>
On Mon, Dec 17, 2018 at 09:06:24PM -0200, Eduardo Habkost wrote:
> On Mon, Dec 17, 2018 at 10:28:58AM -0500, Michael S. Tsirkin wrote:
> > On Fri, Dec 14, 2018 at 02:10:41PM +0100, David Hildenbrand wrote:
> > > These are the two leftovers from
> > > [PATCH v3 0/7] qapi/range/memory-device: fixes and cleanups
> >
> > Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
> >
> > Who's merging this Eduardo?
>
> As I have merged memory-device cleanups before, I can merge it,
> despite MAINTAINERS listing hw/mem/* as part of the ACPI/SMBIOS
> section. What do you prefer?
Pls go ahead.
> --
> Eduardo
prev parent reply other threads:[~2018-12-17 23:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 13:10 [Qemu-devel] [PATCH v5 0/2] range/memory-device: fixes and cleanups David Hildenbrand
2018-12-14 13:10 ` [Qemu-devel] [PATCH v5 1/2] range: add some more functions David Hildenbrand
2018-12-14 13:10 ` [Qemu-devel] [PATCH v5 2/2] memory-device: rewrite address assignment using ranges David Hildenbrand
2018-12-17 8:00 ` Igor Mammedov
2018-12-17 15:28 ` [Qemu-devel] [PATCH v5 0/2] range/memory-device: fixes and cleanups Michael S. Tsirkin
2018-12-17 23:06 ` Eduardo Habkost
2018-12-17 23:08 ` Michael S. Tsirkin [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=20181217180801-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=david@redhat.com \
--cc=dgilbert@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).