From: Jes.Sorensen@redhat.com
To: qemu-devel@nongnu.org
Cc: blauwirbel@gmail.com
Subject: [Qemu-devel] [PATCH 0/1] Avoid compiler error when building block/blkdebug.c with -Wtype-limits
Date: Fri, 10 Sep 2010 16:04:10 +0200 [thread overview]
Message-ID: <1284127451-22092-1-git-send-email-Jes.Sorensen@redhat.com> (raw)
From: Jes Sorensen <Jes.Sorensen@redhat.com>
Hi,
Back to the earlier discussion about building with -Wtype-limits. This
fixes the problem with block/blkdebug.c where it tries to compare an
enum against < 0. I looked at a couple of ways to do this, but I think
this is the least intrusive.
Let me know what you think.
Thanks,
Jes
Jes Sorensen (1):
Avoid compiler error when building block/blkdebug.c with
-Wtype-limits
block/blkdebug.c | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)
next reply other threads:[~2010-09-10 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 14:04 Jes.Sorensen [this message]
2010-09-10 14:04 ` [Qemu-devel] [PATCH 1/1] Avoid compiler error when building block/blkdebug.c with -Wtype-limits Jes.Sorensen
2010-09-10 17:05 ` [Qemu-devel] " Blue Swirl
2010-09-10 17:15 ` Jes Sorensen
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=1284127451-22092-1-git-send-email-Jes.Sorensen@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=blauwirbel@gmail.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).