From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Alex Vesker <valex@nvidia.com>
Subject: |WARNING| pw116678 [v1 15/19] net/mlx5/hws: Add HWS matcher object
Date: Thu, 22 Sep 2022 21:08:27 +0200 (CEST) [thread overview]
Message-ID: <20220922190827.8C14B121F02@dpdk.org> (raw)
In-Reply-To: <20220922190345.394-16-valex@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/116678
_coding style issues_
WARNING:TYPO_SPELLING: 'efficent' may be misspelled - perhaps 'efficient'?
#126:
and from there to other objects. The matcher allows efficent
WARNING:LONG_LINE_COMMENT: line length of 111 exceeds 100 columns
#145: FILE: drivers/net/mlx5/hws/mlx5dr_matcher.c:2:
+ * Copyright (c) Copyright (c) 2022 NVIDIA Corporation 2021 NVIDIA CORPORATION. All rights reserved. Affiliates
WARNING:LONG_LINE: line length of 107 exceeds 100 columns
#390: FILE: drivers/net/mlx5/hws/mlx5dr_matcher.c:247:
+ devx_obj = mlx5dr_pool_chunk_get_base_devx_obj_mirror(stc_pool, &default_stc->default_hit);
CHECK:SPACING: spaces preferred around that '-' (ctx:VxV)
#567: FILE: drivers/net/mlx5/hws/mlx5dr_matcher.c:424:
+ matcher->mt[i-1]->definer);
^
WARNING:TYPO_SPELLING: 'destory' may be misspelled - perhaps 'destroy'?
#787: FILE: drivers/net/mlx5/hws/mlx5dr_matcher.c:644:
+ goto destory_and_disconnect;
WARNING:TYPO_SPELLING: 'destory' may be misspelled - perhaps 'destroy'?
#793: FILE: drivers/net/mlx5/hws/mlx5dr_matcher.c:650:
+destory_and_disconnect:
ERROR:CODE_INDENT: code indent should use tabs where possible
#1014: FILE: drivers/net/mlx5/hws/mlx5dr_matcher.c:871:
+ rte_errno = EINVAL;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#1014: FILE: drivers/net/mlx5/hws/mlx5dr_matcher.c:871:
+ rte_errno = EINVAL;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#1015: FILE: drivers/net/mlx5/hws/mlx5dr_matcher.c:872:
+ return NULL;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#1015: FILE: drivers/net/mlx5/hws/mlx5dr_matcher.c:872:
+ return NULL;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#1021: FILE: drivers/net/mlx5/hws/mlx5dr_matcher.c:878:
+ rte_errno = ENOMEM;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#1021: FILE: drivers/net/mlx5/hws/mlx5dr_matcher.c:878:
+ rte_errno = ENOMEM;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#1022: FILE: drivers/net/mlx5/hws/mlx5dr_matcher.c:879:
+ return NULL;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#1022: FILE: drivers/net/mlx5/hws/mlx5dr_matcher.c:879:
+ return NULL;$
WARNING:LONG_LINE_COMMENT: line length of 111 exceeds 100 columns
#1071: FILE: drivers/net/mlx5/hws/mlx5dr_matcher.h:2:
+ * Copyright (c) Copyright (c) 2022 NVIDIA Corporation 2021 NVIDIA CORPORATION. All rights reserved. Affiliates
total: 4 errors, 10 warnings, 1 checks, 996 lines checked
parent reply other threads:[~2022-09-22 19:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220922190345.394-16-valex@nvidia.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220922190827.8C14B121F02@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=valex@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).