aboutsummaryrefslogtreecommitdiffstats
path: root/fs/btrfs/tests/extent-buffer-tests.c
diff options
context:
space:
mode:
authorFilipe Manana <[email protected]>2020-09-08 10:27:24 +0000
committerDavid Sterba <[email protected]>2020-10-07 10:13:17 +0000
commit0cbb5bdfea2675f4b9749f99120a79f9e0a28600 (patch)
treea2e9d5bd3a29abc90132ffbf44d7028aff943aec /fs/btrfs/tests/extent-buffer-tests.c
parentbtrfs: rename btrfs_punch_hole_range() to a more generic name (diff)
downloadkernel-0cbb5bdfea2675f4b9749f99120a79f9e0a28600.tar.gz
kernel-0cbb5bdfea2675f4b9749f99120a79f9e0a28600.zip
btrfs: rename btrfs_insert_clone_extent() to a more generic name
Now that we use the same mechanism to replace all the extents in a file range with either a hole, an existing extent (when cloning) or a new extent (when using fallocate), the name of btrfs_insert_clone_extent() no longer reflects its genericity. So rename it to btrfs_insert_replace_extent(), since what it does is to either insert an existing extent or a new extent into a file range. Reviewed-by: Josef Bacik <[email protected]> Signed-off-by: Filipe Manana <[email protected]> Reviewed-by: David Sterba <[email protected]> Signed-off-by: David Sterba <[email protected]>
Diffstat (limited to 'fs/btrfs/tests/extent-buffer-tests.c')
0 files changed, 0 insertions, 0 deletions