From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: [Patch] btrfsck.c: bit-fields should be unsigned
Date: Mon, 19 Jan 2009 22:28:29 +0800 [thread overview]
Message-ID: <20090119142829.GB8507@hack.private> (raw)
bit-fields should be unsigned.
Signed-off-by: WANG Cong <wangcong@zeuux.org>
---
diff --git a/btrfsck.c b/btrfsck.c
index 4a41e6d..1bf4064 100644
--- a/btrfsck.c
+++ b/btrfsck.c
@@ -60,10 +60,10 @@ struct extent_record {
struct inode_backref {
struct list_head list;
- int found_dir_item:1;
- int found_dir_index:1;
- int found_inode_ref:1;
- int filetype:8;
+ unsigned int found_dir_item:1;
+ unsigned int found_dir_index:1;
+ unsigned int found_inode_ref:1;
+ unsigned int filetype:8;
int errors;
u64 dir;
u64 index;
@@ -83,13 +83,13 @@ struct inode_backref {
struct inode_record {
struct list_head backrefs;
- int checked:1;
- int found_inode_item:1;
- int found_dir_item:1;
- int found_file_extent:1;
- int found_csum_item:1;
- int some_csum_missing:1;
- int nodatasum:1;
+ unsigned int checked:1;
+ unsigned int found_inode_item:1;
+ unsigned int found_dir_item:1;
+ unsigned int found_file_extent:1;
+ unsigned int found_csum_item:1;
+ unsigned int some_csum_missing:1;
+ unsigned int nodatasum:1;
int errors;
u64 ino;
reply other threads:[~2009-01-19 14:28 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=20090119142829.GB8507@hack.private \
--to=xiyou.wangcong@gmail.com \
--cc=linux-btrfs@vger.kernel.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