diff options
| author | Josef Bacik <josef@toxicpanda.com> | 2020-10-09 16:28:18 +0300 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2021-02-09 00:58:57 +0300 |
| commit | 91e79a83fff663283341c8c29293faec8255099a (patch) | |
| tree | d87ad1063ebf76024aac5f8f81cdb8c28781c849 /tools/perf/scripts/python/mem-phys-addr.py | |
| parent | 8898038309876e5b8e535eac9d4b9fe4e3d6f5b3 (diff) | |
| download | linux-91e79a83fff663283341c8c29293faec8255099a.tar.xz | |
btrfs: make flush_space take a enum btrfs_flush_state instead of int
I got a automated message from somebody who runs clang against our
kernels and it's because I used the wrong enum type for what I passed
into flush_space, caught by -Wenum-conversion. Change the argument to
be explicitly the enum we're expecting to make everything consistent.
Maybe eventually gcc will catch errors like this.
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
Signed-off-by: Josef Bacik <josef@toxicpanda.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions
