From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Frank Blaschka <blaschka@linux.vnet.ibm.com>
Cc: borntraeger@de.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V2] s390x/pci: avoid sign extension in stpcifc
Date: Fri, 23 Jan 2015 15:10:38 +0100 [thread overview]
Message-ID: <20150123151038.1448a873.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <1421855429-36385-1-git-send-email-blaschka@linux.vnet.ibm.com>
On Wed, 21 Jan 2015 16:50:29 +0100
Frank Blaschka <blaschka@linux.vnet.ibm.com> wrote:
> this patch avoids sign extension and fixes a data conversion
> bug in stpcifc. Both issues where found by Coverity.
>
> Signed-off-by: Frank Blaschka <blaschka@linux.vnet.ibm.com>
> ---
> hw/s390x/s390-pci-inst.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Applied to my s390-next branch.
prev parent reply other threads:[~2015-01-23 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 15:50 [Qemu-devel] [PATCH V2] s390x/pci: avoid sign extension in stpcifc Frank Blaschka
2015-01-23 7:44 ` Markus Armbruster
2015-01-23 14:10 ` Cornelia Huck [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=20150123151038.1448a873.cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=blaschka@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--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).