automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jakub Wysocki <jakubx.wysocki@intel.com>
Subject: |WARNING| pw112771 [PATCH] crypto/scheduler: fix qp_id in scheduler failover
Date: Wed, 15 Jun 2022 15:14:58 +0200 (CEST)	[thread overview]
Message-ID: <20220615131458.DC780123450@dpdk.org> (raw)
In-Reply-To: <20220615131349.20315-1-jakubx.wysocki@intel.com>

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

_coding style issues_


ERROR:CODE_INDENT: code indent should use tabs where possible
#80: FILE: drivers/crypto/scheduler/scheduler_failover.c:160:
+        sched_ctx->workers[PRIMARY_WORKER_IDX].qp_id = i;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#80: FILE: drivers/crypto/scheduler/scheduler_failover.c:160:
+        sched_ctx->workers[PRIMARY_WORKER_IDX].qp_id = i;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#81: FILE: drivers/crypto/scheduler/scheduler_failover.c:161:
+        sched_ctx->workers[SECONDARY_WORKER_IDX].qp_id = i;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#81: FILE: drivers/crypto/scheduler/scheduler_failover.c:161:
+        sched_ctx->workers[SECONDARY_WORKER_IDX].qp_id = i;$

ERROR:TRAILING_WHITESPACE: trailing whitespace
#82: FILE: drivers/crypto/scheduler/scheduler_failover.c:162:
+        $

ERROR:CODE_INDENT: code indent should use tabs where possible
#82: FILE: drivers/crypto/scheduler/scheduler_failover.c:162:
+        $

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#82: FILE: drivers/crypto/scheduler/scheduler_failover.c:162:
+        $

total: 4 errors, 3 warnings, 9 lines checked

       reply	other threads:[~2022-06-15 13:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220615131349.20315-1-jakubx.wysocki@intel.com>
2022-06-15 13:14 ` checkpatch [this message]
2022-06-15 13:59 ` |SUCCESS| " 0-day Robot

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=20220615131458.DC780123450@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=jakubx.wysocki@intel.com \
    --cc=test-report@dpdk.org \
    /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).