From: Alex Williamson <alex.williamson@redhat.com>
To: peter.maydell@linaro.org, aliguori@amazon.com
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 0/2] vfio pull for QEMU 2.0
Date: Tue, 25 Mar 2014 12:30:10 -0600 [thread overview]
Message-ID: <20140325182903.6587.14357.stgit@bling.home> (raw)
Peter & Anthony,
The following changes since commit 839a5547574e57cce62f49bfc50fe1f04b00589a:
Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20140324' into staging (2014-03-24 19:25:09 +0000)
are available in the git repository at:
git://github.com/awilliam/qemu-vfio.git tags/vfio-pci-for-qemu-20140325.0
for you to fetch changes up to 4e505ddd9af1d5810378a4e7b851f788b1c075ba:
vfio: Cosmetic error reporting fixes (2014-03-25 12:08:52 -0600)
----------------------------------------------------------------
A couple trivial fixes for QEMU 2.0:
- Coding correction that allowed attempts to read the device
ROM after we'd already marked it failed (Bandan)
- Cosmetic error reporting fixes to remove unnecessary new lines
and fix a cut-n-paste wording error (Alex)
----------------------------------------------------------------
Alex Williamson (1):
vfio: Cosmetic error reporting fixes
Bandan Das (1):
vfio: Correction in vfio_rom_read when attempting rom loading
hw/misc/vfio.c | 33 +++++++++++++++------------------
1 file changed, 15 insertions(+), 18 deletions(-)
next reply other threads:[~2014-03-25 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 18:30 Alex Williamson [this message]
2014-03-25 18:30 ` [Qemu-devel] [PULL 1/2] vfio: Correction in vfio_rom_read when attempting rom loading Alex Williamson
2014-03-25 18:30 ` [Qemu-devel] [PULL 2/2] vfio: Cosmetic error reporting fixes Alex Williamson
2014-03-25 19:10 ` [Qemu-devel] [PULL 0/2] vfio pull for QEMU 2.0 Peter Maydell
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=20140325182903.6587.14357.stgit@bling.home \
--to=alex.williamson@redhat.com \
--cc=aliguori@amazon.com \
--cc=peter.maydell@linaro.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).