net: mctp: test: remove skb dumps from test output

We're currently dumping skb info in our fragment input test, which makes
interpreting the TAP test output a bit awkward.

Remove the skb dumps.

Signed-off-by: Jeremy Kerr <jk@codeconstruct.com.au>
Reviewed-by: Simon Horman <horms@kernel.org>
Link: https://patch.msgid.link/20260429-dev-mctp-test-skb-dump-v1-1-13fd5789ef71@codeconstruct.com.au
Signed-off-by: Jakub Kicinski <kuba@kernel.org>

diff --git a/net/mctp/test/route-test.c b/net/mctp/test/route-test.c
index e1033643fab0e2045fef34b42cab87f746761545..fbd6d4e08aef1050f11d4d3628733e9785357b3f 100644 (file)
--- a/net/mctp/test/route-test.c
+++ b/net/mctp/test/route-test.c
@@ -859,12 +859,6 @@ static void mctp_test_route_input_cloned_frag(struct kunit *test)
        skb[0]->data[4] = 0;
        skb[3]->data[4] = 0;
 
-       skb_dump("pkt1 ", skb[0], false);
-       skb_dump("pkt2 ", skb[1], false);
-       skb_dump("pkt3 ", skb[2], false);
-       skb_dump("pkt4 ", skb[3], false);
-       skb_dump("pkt5 ", skb[4], false);
-
        for (int i = 0; i < 5; i++) {
                KUNIT_EXPECT_EQ(test, refcount_read(&skb[i]->users), 1);
                /* Take a reference so we can check refcounts at the end */