From: Thomas Huth <thuth@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] hw/misc/ivshmem: Remove deprecated "ivshmem" legacy device
Date: Tue, 15 Jan 2019 08:11:03 +0100 [thread overview]
Message-ID: <f225360d-8102-ac2e-2b7d-52066348db8f@redhat.com> (raw)
In-Reply-To: <20190114130814-mutt-send-email-mst@kernel.org>
On 2019-01-14 19:08, Michael S. Tsirkin wrote:
> On Mon, Jan 14, 2019 at 04:04:10PM -0200, Eduardo Habkost wrote:
>> On Wed, Dec 19, 2018 at 03:56:30PM +0100, Markus Armbruster wrote:
>>> Thomas Huth <thuth@redhat.com> writes:
>>>
>>>> It's been marked as deprecated in QEMU v2.6.0 already, so really nobody
>>>> should use the legacy "ivshmem" device anymore (but use ivshmem-plain or
>>>> ivshmem-doorbell instead). Time to remove the deprecated device now.
>>>>
>>>> Belatedly also update a mention of the deprecated "ivshmem" in the file
>>>> docs/specs/ivshmem-spec.txt to "ivshmem-doorbell". Missed in commit
>>>> 5400c02b90b ("ivshmem: Split ivshmem-plain, ivshmem-doorbell off ivshmem").
>>>>
>>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>>
>>> Reviewed-by: Markus Armbruster <armbru@redhat.com>
>>
>> Who should merge this?
>
> I can do it.
Thanks, but since there is no dedicated maintainer for ivshmem, I've
already put it in my PULL request yesterday.
Thomas
prev parent reply other threads:[~2019-01-15 7:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 13:13 [Qemu-devel] [PATCH v2] hw/misc/ivshmem: Remove deprecated "ivshmem" legacy device Thomas Huth
2018-12-19 14:56 ` Markus Armbruster
2019-01-14 18:04 ` Eduardo Habkost
2019-01-14 18:08 ` Michael S. Tsirkin
2019-01-15 7:11 ` Thomas Huth [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=f225360d-8102-ac2e-2b7d-52066348db8f@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--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).