David Sterba c1867eb33e 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>		2022-07-25 17:45:39 +02:00
..
btrfs-tests.c	Revert "btrfs: turn fs_info member buffer_radix into XArray"	2022-07-15 19:14:33 +02:00
btrfs-tests.h	btrfs: selftests: Add support for dummy devices	2020-01-23 17:24:34 +01:00
extent-buffer-tests.c	btrfs: clean up chained assignments	2022-07-25 17:45:39 +02:00
extent-io-tests.c	btrfs: selftests: dump extent io tree if extent-io-tree test failed	2022-01-07 14:18:27 +01:00
extent-map-tests.c	btrfs: assert we have a write lock when removing and replacing extent maps	2022-03-14 13:13:50 +01:00
free-space-tests.c	btrfs: track the csum, extent, and free space trees in a rb tree	2022-01-03 15:09:50 +01:00
free-space-tree-tests.c	btrfs: track the csum, extent, and free space trees in a rb tree	2022-01-03 15:09:50 +01:00
inode-tests.c	btrfs: unexport setup_items_for_insert()	2021-10-26 19:08:03 +02:00
qgroup-tests.c	btrfs: track the csum, extent, and free space trees in a rb tree	2022-01-03 15:09:50 +01:00