public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: andyp <andyp@fedoraproject.org>
To: cluster-cvs-relay@redhat.com
Subject: cluster: STABLE3 - libgfs2: Fix 'dubious one-bit signed bitfield' sparse errors
Date: Wed, 19 Aug 2009 14:36:00 -0000	[thread overview]
Message-ID: <20090819143554.151FD120215@lists.fedorahosted.org> (raw)

Gitweb:        http://git.fedorahosted.org/git/cluster.git?p=cluster.git;a=commitdiff;h=495676a83779b50c0d7253c609958636ef1d46a2
Commit:        495676a83779b50c0d7253c609958636ef1d46a2
Parent:        bec3b293d71404d64976a7da223435e98a969769
Author:        Andrew Price <andy@andrewprice.me.uk>
AuthorDate:    Wed Aug 19 09:24:31 2009 +0100
Committer:     Andrew Price <andy@andrewprice.me.uk>
CommitterDate: Wed Aug 19 15:30:15 2009 +0100

libgfs2: Fix 'dubious one-bit signed bitfield' sparse errors

Fix these sparse errors:

libgfs2.h:575:11: error: dubious one-bit signed bitfield
libgfs2.h:576:10: error: dubious one-bit signed bitfield
libgfs2.h:577:13: error: dubious one-bit signed bitfield

Signed-off-by: Andrew Price <andy@andrewprice.me.uk>
Acked-by: Bob Peterson <rpeterso@redhat.com>
---
 gfs2/libgfs2/libgfs2.h |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/gfs2/libgfs2/libgfs2.h b/gfs2/libgfs2/libgfs2.h
index 558283d..b3c9483 100644
--- a/gfs2/libgfs2/libgfs2.h
+++ b/gfs2/libgfs2/libgfs2.h
@@ -572,9 +572,9 @@ extern struct gfs2_inode *gfs_inode_get(struct gfs2_sbd *sdp,
 /* gfs2_log.c */
 struct gfs2_options {
 	char *device;
-	int yes:1;
-	int no:1;
-	int query:1;
+	unsigned int yes:1;
+	unsigned int no:1;
+	unsigned int query:1;
 };
 
 #define MSG_DEBUG       7


                 reply	other threads:[~2009-08-19 14:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20090819143554.151FD120215@lists.fedorahosted.org \
    --to=andyp@fedoraproject.org \
    --cc=cluster-cvs-relay@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 read-only IMAP folder(s) and NNTP newsgroup(s).