From: Stefan Hajnoczi <stefanha@gmail.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] libcacard: Use format specifier %u instead of %d for unsigned values
Date: Mon, 5 Mar 2012 13:18:53 +0000 [thread overview]
Message-ID: <20120305131853.GF28506@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <1330178057-21503-1-git-send-email-sw@weilnetz.de>
On Sat, Feb 25, 2012 at 02:54:17PM +0100, Stefan Weil wrote:
> splint reported warnings for those code statements.
>
> Signed-off-by: Stefan Weil <sw@weilnetz.de>
> ---
> libcacard/vscclient.c | 20 ++++++++++----------
> 1 files changed, 10 insertions(+), 10 deletions(-)
Thanks, applied to the trivial patches tree:
https://github.com/stefanha/qemu/commits/trivial-patches
Stefan
prev parent reply other threads:[~2012-03-05 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-25 13:54 [Qemu-devel] [PATCH] libcacard: Use format specifier %u instead of %d for unsigned values Stefan Weil
2012-03-05 13:18 ` Stefan Hajnoczi [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=20120305131853.GF28506@stefanha-thinkpad.localdomain \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).