maple_tree: remove extra mt_dump calls from test code

Signed-off-by: Liam R. Howlett <Liam.Howlett@Oracle.com>

diff --git a/lib/test_maple_tree.c b/lib/test_maple_tree.c
index f568bbae3402f2f22c92ba25c27d8037260a3f55..86b79f9c019ba6795748f17e771f341e9b399d8e 100644 (file)
--- a/lib/test_maple_tree.c
+++ b/lib/test_maple_tree.c
@@ -31273,8 +31273,6 @@ static noinline void check_alloc_rev_range(struct maple_tree *mt)
 
        mtree_store_range(mt, MTREE_ALLOC_MAX, ULONG_MAX, XA_ZERO_ENTRY,
                          GFP_KERNEL);
-       mt_dump(mt);
-
 #define DEBUG_REV_RANGE 0
        for (i = 0; i < range_cnt; i += 2) {
                /* Inclusive, Inclusive (with the -1) */
@@ -31752,11 +31750,7 @@ static noinline void check_ranges(struct maple_tree *mt)
                check_store_range(mt, val, val, xa_mk_value(val), 0);
                mt_validate(mt);
                val += 10;
-               if (val == 1116)
-                       mt_dump(mt);
                check_store_range(mt, val, val, xa_mk_value(val), 0);
-               if (val == 1116)
-                       mt_dump(mt);
                mt_validate(mt);
 
                val += 39;