From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Adam Dybkowski <adamx.dybkowski@intel.com>
Subject: [dpdk-test-report] |WARNING| pw79019 [PATCH v2 1/1] crypto/scheduler: rename slave to worker
Date: Mon, 28 Sep 2020 16:19:22 +0200 (CEST) [thread overview]
Message-ID: <20200928141922.AAB1D1D98F@dpdk.org> (raw)
In-Reply-To: <20200928141633.396-2-adamx.dybkowski@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/79019
_coding style issues_
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#49:
Subject: [dpdk-dev] [PATCH v2 1/1] crypto/scheduler: rename slave to worker
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#64:
This patch replaces the usage of the word 'slave' with more
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#71:
rte_cryptodev_scheduler_slave_attach is now called
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#73:
rte_cryptodev_scheduler_slave_detach is
WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#75:
rte_cryptodev_scheduler_slaves_get is
WARNING:TYPO_SPELLING: 'SLAVES' may be misspelled - perhaps 'SECONDARIES'?
#78:
Also, the configuration value RTE_CRYPTODEV_SCHEDULER_MAX_NB_SLAVES
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#336: FILE: doc/guides/rel_notes/release_20_11.rst:136:
+* scheduler: Renamed functions ``rte_cryptodev_scheduler_slave_attach``,
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#337: FILE: doc/guides/rel_notes/release_20_11.rst:137:
+ ``rte_cryptodev_scheduler_slave_detach`` and
WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#338: FILE: doc/guides/rel_notes/release_20_11.rst:138:
+ ``rte_cryptodev_scheduler_slaves_get`` to
WARNING:TYPO_SPELLING: 'SLAVES' may be misspelled - perhaps 'SECONDARIES'?
#344: FILE: doc/guides/rel_notes/release_20_11.rst:144:
+ ``RTE_CRYPTODEV_SCHEDULER_MAX_NB_SLAVES`` to
total: 0 errors, 10 warnings, 1865 lines checked
INFO: symbol rte_cryptodev_scheduler_slave_attach is being removed, ensure that it has gone through the deprecation process
INFO: symbol rte_cryptodev_scheduler_slave_detach is being removed, ensure that it has gone through the deprecation process
INFO: symbol rte_cryptodev_scheduler_slaves_get is being removed, ensure that it has gone through the deprecation process
ERROR: symbol rte_cryptodev_scheduler_worker_attach is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_cryptodev_scheduler_worker_detach is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_cryptodev_scheduler_workers_get is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
next parent reply other threads:[~2020-09-28 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200928141633.396-2-adamx.dybkowski@intel.com>
2020-09-28 14:19 ` checkpatch [this message]
2020-09-28 15:55 ` [dpdk-test-report] |SUCCESS| pw79019 " 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=20200928141922.AAB1D1D98F@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).