diff options
author | 2020-09-08 11:27:24 +0100 | |
---|---|---|
committer | 2020-10-07 12:13:17 +0200 | |
commit | 0cbb5bdfea2675f4b9749f99120a79f9e0a28600 (patch) | |
tree | a2e9d5bd3a29abc90132ffbf44d7028aff943aec /tools/perf/scripts/python/export-to-postgresql.py | |
parent | btrfs: rename btrfs_punch_hole_range() to a more generic name (diff) | |
download | wireguard-linux-0cbb5bdfea2675f4b9749f99120a79f9e0a28600.tar.xz wireguard-linux-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 <josef@toxicpanda.com>
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions