From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Bernhard Beschow <shentey@gmail.com>, qemu-devel@nongnu.org
Cc: Jiaxun Yang <jiaxun.yang@flygoat.com>,
qemu-ppc@nongnu.org, qemu-block@nongnu.org,
John Snow <jsnow@redhat.com>, Huacai Chen <chenhuacai@kernel.org>,
BALATON Zoltan <balaton@eik.bme.hu>
Subject: Re: [PATCH v3 0/7] VIA and general PCI IDE cleanup
Date: Tue, 11 Jul 2023 00:12:36 +0200 [thread overview]
Message-ID: <c69143aa-0e01-882c-7f02-84e7d1ed3b33@linaro.org> (raw)
In-Reply-To: <20230531211043.41724-1-shentey@gmail.com>
On 31/5/23 23:10, Bernhard Beschow wrote:
> This series is split off from a more general PCI IDE refactoring aiming for a
> common implementation of the PCI IDE controller specification for all
> TYPE_PCI_IDE models [1].
> Bernhard Beschow (7):
> hw/ide/pci: Expose legacy interrupts as named GPIOs
> hw/ide/via: Wire up IDE legacy interrupts in host device
> hw/isa/vt82c686: Remove via_isa_set_irq()
> hw/ide: Extract IDEBus assignment into bmdma_init()
> hw/ide: Extract bmdma_status_writeb()
> hw/ide/pci: Replace some magic numbers by constants
> hw/ide/piix: Move registration of VMStateDescription to DeviceClass
Queued to mips-next, thanks!
prev parent reply other threads:[~2023-07-10 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230531211043.41724-1-shentey@gmail.com>
[not found] ` <20230531211043.41724-4-shentey@gmail.com>
2023-05-31 21:27 ` [PATCH v3 3/7] hw/isa/vt82c686: Remove via_isa_set_irq() Philippe Mathieu-Daudé
[not found] ` <20230531211043.41724-7-shentey@gmail.com>
2023-05-31 21:25 ` [PATCH v3 6/7] hw/ide/pci: Replace some magic numbers by constants Philippe Mathieu-Daudé
2023-06-01 12:24 ` Mark Cave-Ayland
[not found] ` <20230531211043.41724-8-shentey@gmail.com>
2023-06-01 12:26 ` [PATCH v3 7/7] hw/ide/piix: Move registration of VMStateDescription to DeviceClass Mark Cave-Ayland
2023-07-10 21:27 ` [PATCH v3 0/7] VIA and general PCI IDE cleanup Bernhard Beschow
2023-07-10 22:12 ` Philippe Mathieu-Daudé [this message]
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=c69143aa-0e01-882c-7f02-84e7d1ed3b33@linaro.org \
--to=philmd@linaro.org \
--cc=balaton@eik.bme.hu \
--cc=chenhuacai@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=jsnow@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=shentey@gmail.com \
/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).