From: Bernhard Beschow <shentey@gmail.com>
To: qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Hervé Poussineau" <hpoussin@reactos.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Bernhard Beschow" <shentey@gmail.com>
Subject: [PATCH 0/2] PC: Create RTC controllers in south bridges
Date: Fri, 19 May 2023 10:47:32 +0200 [thread overview]
Message-ID: <20230519084734.220480-1-shentey@gmail.com> (raw)
This series contains two patches originating from the PIIX consolidation series
[1]. Since the two patches represent general PC code modernization (ICH9 is
modernized as well) and since the PIIX consolidation series is still under
discussion it made sense to split off these patches.
Testing done:
* `make check`
* `make check-avocado`
[1] https://lore.kernel.org/qemu-devel/20230518172747-mutt-send-email-mst@kernel.org/
Bernhard Beschow (2):
hw/i386/pc: Create RTC controllers in south bridges
hw/i386/pc: No need for rtc_state to be an out-parameter
include/hw/i386/pc.h | 2 +-
include/hw/southbridge/ich9.h | 2 ++
include/hw/southbridge/piix.h | 3 +++
hw/i386/pc.c | 16 +++++++++++++---
hw/i386/pc_piix.c | 10 +++++++++-
hw/i386/pc_q35.c | 4 +++-
hw/isa/lpc_ich9.c | 8 ++++++++
hw/isa/piix3.c | 15 +++++++++++++++
hw/isa/Kconfig | 2 ++
9 files changed, 56 insertions(+), 6 deletions(-)
--
2.40.1
next reply other threads:[~2023-05-19 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 8:47 Bernhard Beschow [this message]
2023-05-19 8:47 ` [PATCH 1/2] hw/i386/pc: Create RTC controllers in south bridges Bernhard Beschow
2023-05-19 8:55 ` Michael S. Tsirkin
2023-05-19 8:47 ` [PATCH 2/2] hw/i386/pc: No need for rtc_state to be an out-parameter Bernhard Beschow
2023-05-25 15:50 ` [PATCH 0/2] PC: Create RTC controllers in south bridges Mark Cave-Ayland
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=20230519084734.220480-1-shentey@gmail.com \
--to=shentey@gmail.com \
--cc=aurelien@aurel32.net \
--cc=eduardo@habkost.net \
--cc=hpoussin@reactos.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).