From: David Kiarie <davidkiarie4@gmail.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, jan.kiszka@web.de, mst@redhat.com,
peterx@redhat.com, pbonzini@redhat.com, sw@weilnetz.de,
David Kiarie <davidkiarie4@gmail.com>
Subject: [Qemu-devel] [PATCH V2] Coverity Fix
Date: Sat, 1 Oct 2016 20:06:00 +0300 [thread overview]
Message-ID: <1475341561-32440-1-git-send-email-davidkiarie4@gmail.com> (raw)
This patch fixes a few issues reported by coverity scan in file hw/i386/amd_iommu.c
V2 includes a fix and suggestion from Stefan Weil.
David Kiarie (1):
hw/iommu: Fix problems reported by Coverity scan
hw/i386/amd_iommu.c | 16 ++++++++++------
1 file changed, 10 insertions(+), 6 deletions(-)
--
2.1.4
next reply other threads:[~2016-10-01 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 17:06 David Kiarie [this message]
2016-10-01 17:06 ` [Qemu-devel] [PATCH V2] hw/iommu: Fix problems reported by Coverity scan David Kiarie
2016-10-01 18:24 ` no-reply
2016-10-03 8:58 ` Paolo Bonzini
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=1475341561-32440-1-git-send-email-davidkiarie4@gmail.com \
--to=davidkiarie4@gmail.com \
--cc=jan.kiszka@web.de \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).