automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Alex Vesker <valex@nvidia.com>
Subject: |WARNING| pw116675 [v1 13/19] net/mlx5/hws: Add HWS context object
Date: Thu, 22 Sep 2022 21:08:34 +0200 (CEST)	[thread overview]
Message-ID: <20220922190834.2F2F7121F02@dpdk.org> (raw)
In-Reply-To: <20220922190345.394-14-valex@nvidia.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/116675

_coding style issues_


WARNING:LONG_LINE_COMMENT: line length of 111 exceeds 100 columns
#141: FILE: drivers/net/mlx5/hws/mlx5dr_context.c:2:
+ * Copyright (c) Copyright (c) 2022 NVIDIA Corporation 2021 NVIDIA CORPORATION. All rights reserved. Affiliates

ERROR:SPACING: space prohibited before that ',' (ctx:WxV)
#165: FILE: drivers/net/mlx5/hws/mlx5dr_context.c:26:
+			DR_LOG(ERR, "Failed to allocate STC pool [%d]" ,i);
 			                                               ^

ERROR:SPACING: space required after that ',' (ctx:WxV)
#165: FILE: drivers/net/mlx5/hws/mlx5dr_context.c:26:
+			DR_LOG(ERR, "Failed to allocate STC pool [%d]" ,i);
 			                                               ^

ERROR:SPACING: space required before the open brace '{'
#244: FILE: drivers/net/mlx5/hws/mlx5dr_context.c:105:
+	if (!caps->wqe_based_update){

WARNING:LONG_LINE_COMMENT: line length of 111 exceeds 100 columns
#369: FILE: drivers/net/mlx5/hws/mlx5dr_context.h:2:
+ * Copyright (c) Copyright (c) 2022 NVIDIA Corporation 2021 NVIDIA CORPORATION. All rights reserved. Affiliates

total: 3 errors, 2 warnings, 0 checks, 262 lines checked

           reply	other threads:[~2022-09-22 19:08 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20220922190345.394-14-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=20220922190834.2F2F7121F02@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).