btrfs: clean up chained assignments
authorDavid Sterba <dsterba@suse.com>
Tue, 21 Jun 2022 16:40:48 +0000 (18:40 +0200)
committerDavid Sterba <dsterba@suse.com>
Mon, 25 Jul 2022 15:45:39 +0000 (17:45 +0200)
commitc1867eb33e15b93bca02b7ecde905e3042d90f22
tree2b2b280ce2b6953f914ce374e19660c9226535cc
parentac0677348f3c2373183323f20ccfebe7cb00f9ab
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>
fs/btrfs/dev-replace.c
fs/btrfs/file.c
fs/btrfs/free-space-cache.c
fs/btrfs/inode.c
fs/btrfs/reflink.c
fs/btrfs/tests/extent-buffer-tests.c
fs/btrfs/transaction.c
fs/btrfs/volumes.c