btrfs: tracepoints: remove double negation in finish ordered extent event

There is no need to add a double negation (!!) to the update field because
the field has a boolean type.

Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>

diff --git a/include/trace/events/btrfs.h b/include/trace/events/btrfs.h
index ec1df8b94517c5dcaa5eb6448f20e7c03c36f766..99ae9c923070a0472e37f326e0c7d16a0baef751 100644 (file)
--- a/include/trace/events/btrfs.h
+++ b/include/trace/events/btrfs.h
@@ -670,7 +670,7 @@ TRACE_EVENT(btrfs_finish_ordered_extent,
        TP_printk_btrfs("root=%llu(%s) ino=%llu start=%llu len=%llu uptodate=%d",
                  show_root_type(__entry->root_objectid),
                  __entry->ino, __entry->start,
-                 __entry->len, !!__entry->uptodate)
+                 __entry->len, __entry->uptodate)
 );
 
 DECLARE_EVENT_CLASS(btrfs__writepage,