From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Adam Dybkowski <adamx.dybkowski@intel.com>
Subject: [dpdk-test-report] |WARNING| pw74612 [PATCH] crypto/scheduler: replace usage of master/slave
Date: Wed, 22 Jul 2020 12:17:10 +0200 (CEST) [thread overview]
Message-ID: <20200722101710.49B911BFFA@dpdk.org> (raw)
In-Reply-To: <20200722101522.6531-1-adamx.dybkowski@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/74612
_coding style issues_
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#45:
Subject: [dpdk-dev] [PATCH] crypto/scheduler: replace usage of master/slave
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#45:
Subject: [dpdk-dev] [PATCH] crypto/scheduler: replace usage of master/slave
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#60:
This patch replaces the usage of master/slave in QAT PMD and
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#60:
This patch replaces the usage of master/slave in QAT PMD and
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#266: FILE: doc/guides/rel_notes/deprecation.rst:146:
+* scheduler: The functions ``rte_cryptodev_scheduler_slave_attach``,
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#267: FILE: doc/guides/rel_notes/deprecation.rst:147:
+ ``rte_cryptodev_scheduler_slave_detach`` and
WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#268: FILE: doc/guides/rel_notes/deprecation.rst:148:
+ ``rte_cryptodev_scheduler_slaves_get`` will be replaced by
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#378: FILE: drivers/crypto/scheduler/rte_cryptodev_scheduler.c:163:
+rte_cryptodev_scheduler_slave_attach(uint8_t scheduler_id, uint8_t worker_id)
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#446: FILE: drivers/crypto/scheduler/rte_cryptodev_scheduler.c:232:
+rte_cryptodev_scheduler_slave_detach(uint8_t scheduler_id, uint8_t worker_id)
WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#518: FILE: drivers/crypto/scheduler/rte_cryptodev_scheduler.c:503:
+rte_cryptodev_scheduler_slaves_get(uint8_t scheduler_id, uint8_t *workers)
WARNING:TYPO_SPELLING: 'SLAVES' may be misspelled - perhaps 'SECONDARIES'?
#577: FILE: drivers/crypto/scheduler/rte_cryptodev_scheduler.h:28:
+#ifdef RTE_CRYPTODEV_SCHEDULER_MAX_NB_SLAVES
WARNING:TYPO_SPELLING: 'SLAVES' may be misspelled - perhaps 'SECONDARIES'?
#579: FILE: drivers/crypto/scheduler/rte_cryptodev_scheduler.h:30:
+ RTE_CRYPTODEV_SCHEDULER_MAX_NB_SLAVES
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#612: FILE: drivers/crypto/scheduler/rte_cryptodev_scheduler.h:129:
+rte_cryptodev_scheduler_slave_attach(uint8_t scheduler_id, uint8_t worker_id);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#635: FILE: drivers/crypto/scheduler/rte_cryptodev_scheduler.h:149:
+rte_cryptodev_scheduler_slave_detach(uint8_t scheduler_id, uint8_t worker_id);
WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#667: FILE: drivers/crypto/scheduler/rte_cryptodev_scheduler.h:233:
+rte_cryptodev_scheduler_slaves_get(uint8_t scheduler_id, uint8_t *workers);
total: 0 errors, 15 warnings, 1838 lines checked
next parent reply other threads:[~2020-07-22 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200722101522.6531-1-adamx.dybkowski@intel.com>
2020-07-22 10:17 ` checkpatch [this message]
2020-07-22 11:57 ` [dpdk-test-report] |SUCCESS| pw74612 " 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=20200722101710.49B911BFFA@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=adamx.dybkowski@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).