btrfs: simplify IS_ERR/PTR_ERR checks

IS_ERR(p) && PTR_ERR(p) == n is a weird way to spell p == ERR_PTR(n).

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Reviewed-by: David Sterba <dsterba@suse.com>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
[ update changelog ]
Signed-off-by: David Sterba <dsterba@suse.com>

1 files changed, 2 insertions, 3 deletions

diff --git a/fs/btrfs/tree-log.c b/fs/btrfs/tree-log.c
index 730b97dee955..1650dc44a5e3 100644
--- a/fs/btrfs/tree-log.c
+++ b/fs/btrfs/tree-log.c
@@ -2181,7 +2181,7 @@ again:
                                                      dir_key->offset,
                                                      name, name_len, 0);
                 }
-                if (!log_di || (IS_ERR(log_di) && PTR_ERR(log_di) == -ENOENT)) {
+                if (!log_di || log_di == ERR_PTR(-ENOENT)) {
                         btrfs_dir_item_key_to_cpu(eb, di, &location);
                         btrfs_release_path(path);
                         btrfs_release_path(log_path);
@@ -5011,8 +5011,7 @@ again:
                                  * we don't need to do more work nor fallback to
                                  * a transaction commit.
                                  */
-                                if (IS_ERR(other_inode) &&
-                                    PTR_ERR(other_inode) == -ENOENT) {
+                                if (other_inode == ERR_PTR(-ENOENT)) {
                                         goto next_key;
                                 } else if (IS_ERR(other_inode)) {
                                         err = PTR_ERR(other_inode);