From: Luiz Capitulino <lcapitulino@redhat.com>
To: qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, qzhang@redhat.com, eblake@redhat.com,
armbru@redhat.com
Subject: [Qemu-devel] [PATCH v4 0/2]: hmp: integer parsing fixes
Date: Mon, 7 May 2012 11:09:25 -0300 [thread overview]
Message-ID: <1336399767-16248-1-git-send-email-lcapitulino@redhat.com> (raw)
I've decided to implement Markus's suggestion (ie. check only for ERANGE) to
avoid needless discussions on a simple thing...
o V4
- Check only for ERANGE in expr_unary() [Markus]
monitor.c | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
next reply other threads:[~2012-05-07 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 14:09 Luiz Capitulino [this message]
2012-05-07 14:09 ` [Qemu-devel] [PATCH 1/2] hmp: expr_unary(): check for overflow in strtoul()/strtoull() Luiz Capitulino
2012-05-07 14:09 ` [Qemu-devel] [PATCH 2/2] hmp: fix bad value conversion for M type Luiz Capitulino
2012-05-07 14:18 ` [Qemu-devel] [PATCH v4 0/2]: hmp: integer parsing fixes Eric Blake
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=1336399767-16248-1-git-send-email-lcapitulino@redhat.com \
--to=lcapitulino@redhat.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qzhang@redhat.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).