From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Thomas Huth" <huth@tuxfamily.org>,
"Laurent Vivier" <laurent@vivier.eu>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PATCH v2 0/6] hw/m68k: Strengthen QOM/SysBus API uses
Date: Tue, 24 Oct 2023 10:30:03 +0200 [thread overview]
Message-ID: <20231024083010.12453-1-philmd@linaro.org> (raw)
All series reviewed.
v2:
- Addressed Thomas comments in patches 1-2
- Added R-b tags
Avoid QOM objects poking at each other internals:
- Pass "link" properties
- Access MMIO via SysBus API
- Simplify using sysbus_create_simple()
Philippe Mathieu-Daudé (6):
hw/m68k/irqc: Pass CPU using QOM link property
hw/m68k/mcf5206: Pass CPU using QOM link property
hw/m68k/mcf_intc: Expose MMIO region via SysBus API
hw/m68k/mcf_intc: Pass CPU using QOM link property
hw/m68k/next-cube: Do not open-code sysbus_create_simple()
hw/m68k/virt: Do not open-code sysbus_create_simple()
include/hw/intc/m68k_irqc.h | 1 +
hw/intc/m68k_irqc.c | 10 +++++++++-
hw/m68k/an5206.c | 6 ++++--
hw/m68k/mcf5206.c | 9 ++++++++-
hw/m68k/mcf_intc.c | 21 ++++++++++++++-------
hw/m68k/next-cube.c | 9 ++-------
hw/m68k/virt.c | 9 ++++-----
7 files changed, 42 insertions(+), 23 deletions(-)
--
2.41.0
next reply other threads:[~2023-10-24 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 8:30 Philippe Mathieu-Daudé [this message]
2023-10-24 8:30 ` [PATCH v2 1/6] hw/m68k/irqc: Pass CPU using QOM link property Philippe Mathieu-Daudé
2023-10-24 8:30 ` [PATCH v2 2/6] hw/m68k/mcf5206: " Philippe Mathieu-Daudé
2023-10-24 8:30 ` [PATCH v2 3/6] hw/m68k/mcf_intc: Expose MMIO region via SysBus API Philippe Mathieu-Daudé
2023-10-24 8:30 ` [PATCH v2 4/6] hw/m68k/mcf_intc: Pass CPU using QOM link property Philippe Mathieu-Daudé
2023-10-24 8:30 ` [PATCH v2 5/6] hw/m68k/next-cube: Do not open-code sysbus_create_simple() Philippe Mathieu-Daudé
2023-10-24 8:30 ` [PATCH v2 6/6] hw/m68k/virt: " Philippe Mathieu-Daudé
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=20231024083010.12453-1-philmd@linaro.org \
--to=philmd@linaro.org \
--cc=huth@tuxfamily.org \
--cc=laurent@vivier.eu \
--cc=mark.cave-ayland@ilande.co.uk \
--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).