From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ciara Power <ciara.power@intel.com>
Subject: [dpdk-test-report] |WARNING| pw89240 [PATCH 3/6] test/crypto: refactor to use sub-testsuites
Date: Tue, 16 Mar 2021 15:34:05 +0100 (CET) [thread overview]
Message-ID: <20210316143405.6A5602BE3@dpdk.org> (raw)
In-Reply-To: <20210316143253.3849182-4-ciara.power@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/89240
_coding style issues_
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#640: FILE: app/test/test_cryptodev.c:13316:
+ if (test_scheduler_attach_slave_op() < 0)
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#657: FILE: app/test/test_cryptodev.c:13326:
+ if (test_scheduler_attach_slave_op() < 0)
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#674: FILE: app/test/test_cryptodev.c:13336:
+ if (test_scheduler_attach_slave_op() < 0)
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#691: FILE: app/test/test_cryptodev.c:13346:
+ if (test_scheduler_attach_slave_op() < 0)
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#704: FILE: app/test/test_cryptodev.c:13356:
+ test_scheduler_detach_slave_op();
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1811: FILE: app/test/test_cryptodev.c:14857:
+ TEST_CASE(test_scheduler_attach_slave_op),
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1816: FILE: app/test/test_cryptodev.c:14862:
+ TEST_CASE(test_scheduler_detach_slave_op),
total: 0 errors, 7 warnings, 2124 lines checked
parent reply other threads:[~2021-03-16 14:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210316143253.3849182-4-ciara.power@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=20210316143405.6A5602BE3@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ciara.power@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).