From: Bernhard Beschow <shentey@gmail.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Bernhard Beschow <shentey@gmail.com>
Subject: [PATCH v3 0/3] QOM improvements for rtc/mc146818rtc
Date: Sun, 29 May 2022 20:40:03 +0200 [thread overview]
Message-ID: <20220529184006.10712-1-shentey@gmail.com> (raw)
v3:
* "iobase" is now u16 (Philippe)
v2:
* Explicitly fail with &error_abort rather than NULL (Mark)
* Explicitly fail with &error_abort rather than NULL in existing code (me)
* Unexport rather than remove RTC_ISA_BASE (Mark)
* Use object_property_get_*u*int() also for "iobase" (me)
v1:
This little series enhances QOM support for mc146818rtc:
* makes microvm-dt respect mc146818rtc's IRQ number set by QOM property and
* adds an io_base QOM property similar to other ISA devices
Bernhard Beschow (3):
hw/i386/microvm-dt: Force explicit failure if retrieving QOM property
fails
hw/i386/microvm-dt: Determine mc146818rtc's IRQ number from QOM
property
rtc/mc146818rtc: QOM'ify io_base offset
hw/i386/microvm-dt.c | 9 +++++----
hw/rtc/mc146818rtc.c | 9 ++++++---
include/hw/rtc/mc146818rtc.h | 2 +-
3 files changed, 12 insertions(+), 8 deletions(-)
--
2.36.1
next reply other threads:[~2022-05-29 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 18:40 Bernhard Beschow [this message]
2022-05-29 18:40 ` [PATCH v3 1/3] hw/i386/microvm-dt: Force explicit failure if retrieving QOM property fails Bernhard Beschow
2022-05-29 18:40 ` [PATCH v3 2/3] hw/i386/microvm-dt: Determine mc146818rtc's IRQ number from QOM property Bernhard Beschow
2022-05-29 18:40 ` [PATCH v3 3/3] rtc/mc146818rtc: QOM'ify io_base offset Bernhard Beschow
2022-06-02 21:18 ` [PATCH v3 0/3] QOM improvements for rtc/mc146818rtc Bernhard Beschow
2022-06-10 13:59 ` Philippe Mathieu-Daudé via
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=20220529184006.10712-1-shentey@gmail.com \
--to=shentey@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).