From: Liav Albani <liavalb@gmail.com>
To: qemu-devel@nongnu.org
Cc: jsnow@redhat.com, Liav Albani <liavalb@gmail.com>, qemu-block@nongnu.org
Subject: [PATCH 0/1] hw/ide: share bmdma read and write functions
Date: Sat, 19 Feb 2022 10:08:17 +0200 [thread overview]
Message-ID: <20220219080818.327683-1-liavalb@gmail.com> (raw)
This is a preparation before I send v3 of ich6-ide controller emulation patch.
I figured that it's more trivial to split the changes this way, by extracting
the bmdma functions from via.c and piix.c and sharing them together. Then,
I could easily put these into use when I send v3 of the ich6-ide patch by just
using the already separated functions. This was suggested by BALATON Zoltan when
he submitted a code review on my ich6-ide controller emulation patch.
Liav Albani (1):
hw/ide: share bmdma read and write functions between piix.c and via.c
hw/ide/pci.c | 47 ++++++++++++++++++++++++++++++++++++++++
hw/ide/piix.c | 50 ++-----------------------------------------
hw/ide/via.c | 51 ++------------------------------------------
include/hw/ide/pci.h | 4 ++++
4 files changed, 55 insertions(+), 97 deletions(-)
--
2.35.1
next reply other threads:[~2022-02-19 8:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-19 8:08 Liav Albani [this message]
2022-02-19 8:08 ` [PATCH 1/1] hw/ide: share bmdma read and write functions between piix.c and via.c Liav Albani
2022-02-19 11:19 ` BALATON Zoltan
2022-02-19 13:05 ` Liav Albani
2022-02-19 14:32 ` BALATON Zoltan
2022-02-19 15:57 ` BALATON Zoltan
2022-02-19 17:11 ` Liav Albani
2022-02-19 18:10 ` BALATON Zoltan
2022-09-06 14:26 ` [PATCH 0/1] hw/ide: share bmdma read and write functions Bernhard Beschow
2023-01-09 19:24 ` John Snow
2023-01-10 23:07 ` Bernhard Beschow
[not found] ` <7e7bf877-0300-7a2e-e0a4-f8db6eeae88b@gmail.com>
2023-01-16 20:29 ` John Snow
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=20220219080818.327683-1-liavalb@gmail.com \
--to=liavalb@gmail.com \
--cc=jsnow@redhat.com \
--cc=qemu-block@nongnu.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).