[dpdk-test-report] |WARNING| pw29848 [PATCH] Mellanox ConnectX-5 crashes and mbuf leak
checkpatch at dpdk.org
checkpatch at dpdk.org
Sat Oct 7 00:32:04 CEST 2017
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/29848
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#19:
I figured out deadlock could happen if the Rx queue size is smaller. It is 128
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#202: FILE: drivers/net/mlx5/mlx5_rxtx_vec_sse.c:552:
+ uint16_t elts_idx = rxq->rq_ci & q_mask;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#211: FILE: drivers/net/mlx5/mlx5_rxtx_vec_sse.c:571:
+ elts_idx = rxq->rq_ci & q_mask;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#212: FILE: drivers/net/mlx5/mlx5_rxtx_vec_sse.c:572:
+ for (i = 0; i < MLX5_VPMD_DESCS_PER_LOOP; i += 2)$
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (7, 15)
#212: FILE: drivers/net/mlx5/mlx5_rxtx_vec_sse.c:572:
+ for (i = 0; i < MLX5_VPMD_DESCS_PER_LOOP; i += 2)
+ _mm_storeu_si128((__m128i *)&(*rxq->elts)[elts_idx + i],
ERROR:CODE_INDENT: code indent should use tabs where possible
#213: FILE: drivers/net/mlx5/mlx5_rxtx_vec_sse.c:573:
+ _mm_storeu_si128((__m128i *)&(*rxq->elts)[elts_idx + i],$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#213: FILE: drivers/net/mlx5/mlx5_rxtx_vec_sse.c:573:
+ _mm_storeu_si128((__m128i *)&(*rxq->elts)[elts_idx + i],$
ERROR:CODE_INDENT: code indent should use tabs where possible
#214: FILE: drivers/net/mlx5/mlx5_rxtx_vec_sse.c:574:
+ _mm_set1_epi64x((uintptr_t)&rxq->fake_mbuf));$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#214: FILE: drivers/net/mlx5/mlx5_rxtx_vec_sse.c:574:
+ _mm_set1_epi64x((uintptr_t)&rxq->fake_mbuf));$
ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 3 errors, 7 warnings, 0 checks, 19 lines checked
More information about the test-report
mailing list