From: Li Qiang <liq3ea@163.com>
To: alex.williamson@redhat.com, lvivier@redhat.com
Cc: qemu-trivial@nongnu.org, philmd@redhat.com, liq3ea@gmail.com,
qemu-devel@nongnu.org, Li Qiang <liq3ea@163.com>
Subject: [Qemu-devel] [PATCH v2 0/4] hw: vfio: some trivial fix
Date: Tue, 21 May 2019 08:15:39 -0700 [thread overview]
Message-ID: <20190521151543.92274-1-liq3ea@163.com> (raw)
These patchset fix some trivial issues,
The first patch makes the code more QOMConventions.
The second decouples VMStateDescription's name with
QOM TypeInfo's name.
The third fixes a typo.
The fourth reduce duplicated code.
Change since v1:
Add more commit message.
Li Qiang (4):
vfio: pci: make "vfio-pci-nohotplug" as MACRO
hw: vfio: drop TYPE_FOO MACRO in VMStateDescription
vfio: platform: fix a typo
pci: msix: move 'MSIX_CAP_LENGTH' to header file
hw/pci/msix.c | 2 --
hw/vfio/amd-xgbe.c | 2 +-
hw/vfio/ap.c | 2 +-
hw/vfio/calxeda-xgmac.c | 2 +-
hw/vfio/ccw.c | 2 +-
hw/vfio/pci.c | 8 ++++----
hw/vfio/platform.c | 6 +++---
include/hw/pci/msix.h | 2 ++
8 files changed, 13 insertions(+), 13 deletions(-)
--
2.17.1
next reply other threads:[~2019-05-21 15:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 15:15 Li Qiang [this message]
2019-05-21 15:15 ` [Qemu-devel] [PATCH v2 1/4] vfio: pci: make "vfio-pci-nohotplug" as MACRO Li Qiang
2019-05-22 15:24 ` [Qemu-devel] [Qemu-trivial] " Laurent Vivier
2019-05-21 15:15 ` [Qemu-devel] [PATCH v2 2/4] hw: vfio: drop TYPE_FOO MACRO in VMStateDescription Li Qiang
2019-05-22 15:26 ` [Qemu-devel] [Qemu-trivial] " Laurent Vivier
2019-05-21 15:15 ` [Qemu-devel] [PATCH v2 3/4] vfio: platform: fix a typo Li Qiang
2019-05-22 15:27 ` [Qemu-devel] [Qemu-trivial] " Laurent Vivier
2019-05-21 15:15 ` [Qemu-devel] [PATCH v2 4/4] pci: msix: move 'MSIX_CAP_LENGTH' to header file Li Qiang
2019-05-22 15:28 ` [Qemu-devel] [Qemu-trivial] " Laurent Vivier
2019-05-21 15:37 ` [Qemu-devel] [PATCH v2 0/4] hw: vfio: some trivial fix Alex Williamson
2019-05-21 15:39 ` Philippe Mathieu-Daudé
2019-05-21 15:50 ` Auger Eric
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=20190521151543.92274-1-liq3ea@163.com \
--to=liq3ea@163.com \
--cc=alex.williamson@redhat.com \
--cc=liq3ea@gmail.com \
--cc=lvivier@redhat.com \
--cc=philmd@redhat.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).