From: Anthony PERARD via <qemu-devel@nongnu.org>
To: <qemu-devel@nongnu.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>
Subject: [PULL 0/3] xen queue 2022-06-09
Date: Thu, 9 Jun 2022 15:01:59 +0100 [thread overview]
Message-ID: <20220609140202.45227-1-anthony.perard@citrix.com> (raw)
The following changes since commit 05911658cb46d907fb38cbc0b48d2b652237dc28:
Merge tag 'vfio-updates-20220608.0' of https://gitlab.com/alex.williamson/qemu into staging (2022-06-08 13:38:54 -0700)
are available in the Git repository at:
https://xenbits.xen.org/git-http/people/aperard/qemu-dm.git tags/pull-xen-20220609
for you to fetch changes up to 6a8a8b62bdc8e3d7c5fc0f82ef4583707183b12f:
include/hw/ide: Unexport pci_piix3_xen_ide_unplug() (2022-06-09 14:47:42 +0100)
----------------------------------------------------------------
Xen patches
- PIIX3-IDE Xen cleanup
----------------------------------------------------------------
Bernhard Beschow (3):
hw/ide/piix: Remove redundant "piix3-ide-xen" device class
hw/ide/piix: Add some documentation to pci_piix3_xen_ide_unplug()
include/hw/ide: Unexport pci_piix3_xen_ide_unplug()
hw/i386/pc_piix.c | 3 +--
hw/i386/xen/xen_platform.c | 48 +++++++++++++++++++++++++++++++++++++++++++++-
hw/ide/piix.c | 42 ----------------------------------------
include/hw/ide.h | 3 ---
4 files changed, 48 insertions(+), 48 deletions(-)
next reply other threads:[~2022-06-09 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 14:01 Anthony PERARD via [this message]
2022-06-09 14:02 ` [PULL 1/3] hw/ide/piix: Remove redundant "piix3-ide-xen" device class Anthony PERARD via
2022-06-09 14:02 ` [PULL 2/3] hw/ide/piix: Add some documentation to pci_piix3_xen_ide_unplug() Anthony PERARD via
2022-06-09 14:02 ` [PULL 3/3] include/hw/ide: Unexport pci_piix3_xen_ide_unplug() Anthony PERARD via
2022-06-09 19:52 ` [PULL 0/3] xen queue 2022-06-09 Richard Henderson
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=20220609140202.45227-1-anthony.perard@citrix.com \
--to=qemu-devel@nongnu.org \
--cc=anthony.perard@citrix.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).