btrfs: clean up chained assignments
The chained assignments may be convenient to write, but make readability a bit worse as it's too easy to overlook that there are several values set on the same line while this is rather an exception. Making it consistent everywhere avoids surprises. The pattern where inode times are initialized reuses the first value and the order is mtime, ctime. In other blocks the assignments are expanded so the order of variables is similar to the neighboring code. Signed-off-by: David Sterba <dsterba@suse.com>
This commit is contained in:
@@ -587,7 +587,8 @@ bool btrfs_finish_block_group_to_copy(struct btrfs_device *srcdev,
|
||||
ASSERT(!IS_ERR(em));
|
||||
map = em->map_lookup;
|
||||
|
||||
num_extents = cur_extent = 0;
|
||||
num_extents = 0;
|
||||
cur_extent = 0;
|
||||
for (i = 0; i < map->num_stripes; i++) {
|
||||
/* We have more device extent to copy */
|
||||
if (srcdev != map->stripes[i].dev)
|
||||
|
||||
Reference in New Issue
Block a user