From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49356) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cX7sG-00012q-0b for qemu-devel@nongnu.org; Fri, 27 Jan 2017 09:51:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cX7sA-0000F3-VR for qemu-devel@nongnu.org; Fri, 27 Jan 2017 09:51:36 -0500 From: Thomas Huth Date: Fri, 27 Jan 2017 15:51:28 +0100 Message-Id: <1485528688-29914-1-git-send-email-thuth@redhat.com> Subject: [Qemu-devel] [PATCH] hw/core/or-irq: Mark the device with cannot_instantiate_with_device_add_yet List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alistair Francis , qemu-devel@nongnu.org Cc: qemu-trivial@nongnu.org, Markus Armbruster The "or-irq" device is just used internally. It's strange to see this device showing up in the "-device ?" help text. Let's mark it with cannot_instantiate_with_device_add_yet to hide it from the users. Signed-off-by: Thomas Huth --- hw/core/or-irq.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/hw/core/or-irq.c b/hw/core/or-irq.c index 1ac090d..2487fa3 100644 --- a/hw/core/or-irq.c +++ b/hw/core/or-irq.c @@ -89,6 +89,9 @@ static void or_irq_class_init(ObjectClass *klass, void *data) dc->props = or_irq_properties; dc->realize = or_irq_realize; dc->vmsd = &vmstate_or_irq; + + /* It's just used internally, and should not be exposed to users */ + dc->cannot_instantiate_with_device_add_yet = true; } static const TypeInfo or_irq_type_info = { -- 1.8.3.1