From: "Andreas Färber" <afaerber@suse.de>
To: armbru@redhat.com, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, borntraeger@de.ibm.com,
aliguori@amazon.com, marcel.a@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 00/10] Clean up and fix no_user
Date: Sun, 15 Dec 2013 21:37:07 +0100 [thread overview]
Message-ID: <52AE12F3.4050401@suse.de> (raw)
In-Reply-To: <1385656023-11519-1-git-send-email-armbru@redhat.com>
Am 28.11.2013 17:26, schrieb armbru@redhat.com:
> Markus Armbruster (10):
> qdev: Replace no_user by cannot_instantiate_with_device_add_yet
> sysbus: Set cannot_instantiate_with_device_add_yet
> cpu: Document why cannot_instantiate_with_device_add_yet
> apic: Document why cannot_instantiate_with_device_add_yet
> pci-host: Consistently set cannot_instantiate_with_device_add_yet
> ich9: Document why cannot_instantiate_with_device_add_yet
> piix3 piix4: Clean up use of cannot_instantiate_with_device_add_yet
> vt82c686: Clean up use of cannot_instantiate_with_device_add_yet
> isa: Clean up use of cannot_instantiate_with_device_add_yet
> qdev: Do not let the user try to device_add when it cannot work
I've applied all except for the ISA patch, which doesn't feature a
Reviewed-by yet.
https://github.com/afaerber/qemu-cpu/commits/qom-next
I'd appreciate if some previous reviewer can comment on whether any
issues have been resolved satisfactorily.
Thanks,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-12-15 20:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 16:26 [Qemu-devel] [PATCH v4 00/10] Clean up and fix no_user armbru
2013-11-28 16:26 ` [Qemu-devel] [PATCH v4 01/10] qdev: Replace no_user by cannot_instantiate_with_device_add_yet armbru
2013-11-28 16:26 ` [Qemu-devel] [PATCH v4 02/10] sysbus: Set cannot_instantiate_with_device_add_yet armbru
2013-12-15 20:16 ` Andreas Färber
2013-11-28 16:26 ` [Qemu-devel] [PATCH v4 03/10] cpu: Document why cannot_instantiate_with_device_add_yet armbru
2013-11-28 16:26 ` [Qemu-devel] [PATCH v4 04/10] apic: " armbru
2013-11-28 16:26 ` [Qemu-devel] [PATCH v4 05/10] pci-host: Consistently set cannot_instantiate_with_device_add_yet armbru
2013-11-28 16:26 ` [Qemu-devel] [PATCH v4 06/10] ich9: Document why cannot_instantiate_with_device_add_yet armbru
2013-11-28 16:27 ` [Qemu-devel] [PATCH v4 07/10] piix3 piix4: Clean up use of cannot_instantiate_with_device_add_yet armbru
2013-11-28 16:27 ` [Qemu-devel] [PATCH v4 08/10] vt82c686: " armbru
2013-11-28 16:27 ` [Qemu-devel] [PATCH v4 09/10] isa: " armbru
2013-11-28 16:27 ` [Qemu-devel] [PATCH v4 10/10] qdev: Do not let the user try to device_add when it cannot work armbru
2013-12-15 20:25 ` Andreas Färber
2013-12-16 7:28 ` Markus Armbruster
2013-12-15 20:37 ` Andreas Färber [this message]
2013-12-16 8:21 ` [Qemu-devel] [PATCH v4 00/10] Clean up and fix no_user Markus Armbruster
2013-12-16 8:21 ` Marcel Apfelbaum
2013-12-19 16:40 ` Andreas Färber
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=52AE12F3.4050401@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=marcel.a@redhat.com \
--cc=peter.maydell@linaro.org \
--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).