From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
Subject: [dpdk-test-report] |WARNING| pw77077 [v2 1/2] cryptodev: support enqueue callback functions
Date: Wed, 9 Sep 2020 18:18:05 +0200 (CEST) [thread overview]
Message-ID: <20200909161805.4CF091C0C9@dpdk.org> (raw)
In-Reply-To: <1599549024-195051-1-git-send-email-abhinandan.gujjar@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/77077
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#266: FILE: lib/librte_cryptodev/rte_cryptodev.c:1587:
+ * control plane API */
WARNING:TYPO_SPELLING: 'THRID' may be misspelled - perhaps 'THIRD'?
#268: FILE: lib/librte_cryptodev/rte_cryptodev.c:1589:
+ RTE_QSBR_THRID_INVALID);
total: 0 errors, 2 warnings, 396 lines checked
parent reply other threads:[~2020-09-09 16:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1599549024-195051-1-git-send-email-abhinandan.gujjar@intel.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=20200909161805.4CF091C0C9@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=abhinandan.gujjar@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).