From: Jeremy Kerr Date: Wed, 29 Apr 2026 08:27:31 +0000 (+0800) Subject: net: mctp: test: remove skb dumps from test output X-Git-Url: http://git.ipfire.org/gitweb/index.cgi?a=commitdiff_plain;h=8ca4bff2ff3eb523154eb6bdc8e1efe47d6f9888;p=thirdparty%2Fkernel%2Flinux.git 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 Reviewed-by: Simon Horman Link: https://patch.msgid.link/20260429-dev-mctp-test-skb-dump-v1-1-13fd5789ef71@codeconstruct.com.au Signed-off-by: Jakub Kicinski --- diff --git a/net/mctp/test/route-test.c b/net/mctp/test/route-test.c index e1033643fab0e..fbd6d4e08aef1 100644 --- 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 */