btrfs: drop default value assignments in enums

A few more instances whre we don't need to specify the values as long as
they are the same that enum assigns automatically. All of the enums are
in-memory only and nothing relies on the exact values.

Signed-off-by: David Sterba <dsterba@suse.com>
This commit is contained in:
David Sterba 2019-06-18 20:00:08 +02:00
parent 2792237d0c
commit f262fa8de6
2 changed files with 10 additions and 10 deletions

View File

@ -46,9 +46,9 @@
* *
*/ */
enum { enum {
CHUNK_ALLOC_NO_FORCE = 0, CHUNK_ALLOC_NO_FORCE,
CHUNK_ALLOC_LIMITED = 1, CHUNK_ALLOC_LIMITED,
CHUNK_ALLOC_FORCE = 2, CHUNK_ALLOC_FORCE,
}; };
/* /*
@ -7302,10 +7302,10 @@ wait_block_group_cache_done(struct btrfs_block_group_cache *cache)
} }
enum btrfs_loop_type { enum btrfs_loop_type {
LOOP_CACHING_NOWAIT = 0, LOOP_CACHING_NOWAIT,
LOOP_CACHING_WAIT = 1, LOOP_CACHING_WAIT,
LOOP_ALLOC_CHUNK = 2, LOOP_ALLOC_CHUNK,
LOOP_NO_EMPTY_SIZE = 3, LOOP_NO_EMPTY_SIZE,
}; };
static inline void static inline void

View File

@ -2796,9 +2796,9 @@ static int btrfs_fallocate_update_isize(struct inode *inode,
} }
enum { enum {
RANGE_BOUNDARY_WRITTEN_EXTENT = 0, RANGE_BOUNDARY_WRITTEN_EXTENT,
RANGE_BOUNDARY_PREALLOC_EXTENT = 1, RANGE_BOUNDARY_PREALLOC_EXTENT,
RANGE_BOUNDARY_HOLE = 2, RANGE_BOUNDARY_HOLE,
}; };
static int btrfs_zero_range_check_range_boundary(struct inode *inode, static int btrfs_zero_range_check_range_boundary(struct inode *inode,