From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Anoob Joseph <anoob.joseph@caviumnetworks.com>
Subject: [dpdk-test-report] |WARNING| pw40864 [PATCH 03/16] crypto/cpt/base: add hardware initialization API for CPT
Date: Fri, 8 Jun 2018 18:50:10 +0200 (CEST) [thread overview]
Message-ID: <20180608165010.DFC8E1CFE5@dpdk.org> (raw)
In-Reply-To: <1528476325-15585-4-git-send-email-anoob.joseph@caviumnetworks.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/40864
_coding style issues_
WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#57: FILE: drivers/crypto/cpt/base/cpt8xxx_device.c:1:
+/* SPDX-License-Identifier: BSD-3-Clause
WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#591: FILE: drivers/crypto/cpt/base/cpt_device.c:1:
+/* SPDX-License-Identifier: BSD-3-Clause
WARNING:EMBEDDED_FUNCTION_NAME: Prefer using '"%s...", __func__' to using 'cpt_vf_init', this function's name, in a string
#647: FILE: drivers/crypto/cpt/base/cpt_device.c:57:
+ PMD_DRV_LOG(DEBUG, "%s: cpt_vf_init() done
", cptvf->dev_name);
WARNING:EMBEDDED_FUNCTION_NAME: Prefer using '"%s...", __func__' to using 'cpt_vq_init', this function's name, in a string
#680: FILE: drivers/crypto/cpt/base/cpt_device.c:90:
+ PMD_DRV_LOG(DEBUG, "%s: cpt_vq_init() done
", cptvf->dev_name);
WARNING:TYPO_SPELLING: 'Alignement' may be misspelled - perhaps 'Alignment'?
#844: FILE: drivers/crypto/cpt/base/cpt_device.c:254:
+ /* Alignement wastage */
WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#1148: FILE: drivers/crypto/cpt/base/cpt_vf_mbox.c:1:
+/* SPDX-License-Identifier: BSD-3-Clause
total: 0 errors, 6 warnings, 1297 lines checked
parent reply other threads:[~2018-06-08 16:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1528476325-15585-4-git-send-email-anoob.joseph@caviumnetworks.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=20180608165010.DFC8E1CFE5@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=anoob.joseph@caviumnetworks.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).