summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeremy Kerr <jk@codeconstruct.com.au>2026-04-29 11:27:31 +0300
committerJakub Kicinski <kuba@kernel.org>2026-04-30 23:37:51 +0300
commit8ca4bff2ff3eb523154eb6bdc8e1efe47d6f9888 (patch)
tree36d26d3344ac0fc9ac6ac6fa11cd608c3dd41cbb
parent7c04aa3b2f3751f3eb2370f280eeb8557962ad96 (diff)
downloadlinux-8ca4bff2ff3eb523154eb6bdc8e1efe47d6f9888.tar.xz
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>
-rw-r--r--net/mctp/test/route-test.c6
1 files changed, 0 insertions, 6 deletions
diff --git a/net/mctp/test/route-test.c b/net/mctp/test/route-test.c
index e1033643fab0..fbd6d4e08aef 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 */