* [dpdk-test-report] |WARNING| pw79019 [PATCH v2 1/1] crypto/scheduler: rename slave to worker
[not found] <20200928141633.396-2-adamx.dybkowski@intel.com>
@ 2020-09-28 14:19 ` checkpatch
2020-09-28 15:55 ` [dpdk-test-report] |SUCCESS| pw79019 " 0-day Robot
1 sibling, 0 replies; 2+ messages in thread
From: checkpatch @ 2020-09-28 14:19 UTC (permalink / raw)
To: test-report; +Cc: Adam Dybkowski
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* [dpdk-test-report] |SUCCESS| pw79019 crypto/scheduler: rename slave to worker
[not found] <20200928141633.396-2-adamx.dybkowski@intel.com>
2020-09-28 14:19 ` [dpdk-test-report] |WARNING| pw79019 [PATCH v2 1/1] crypto/scheduler: rename slave to worker checkpatch
@ 2020-09-28 15:55 ` 0-day Robot
1 sibling, 0 replies; 2+ messages in thread
From: 0-day Robot @ 2020-09-28 15:55 UTC (permalink / raw)
To: test-report; +Cc: robot
From: robot@bytheb.org
Test-Label: travis-robot
Test-Status: SUCCESS
http://dpdk.org/patch/79019
_Travis build: passed_
Build URL: https://travis-ci.com/ovsrobot/dpdk/builds/187031533
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-09-28 15:57 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20200928141633.396-2-adamx.dybkowski@intel.com>
2020-09-28 14:19 ` [dpdk-test-report] |WARNING| pw79019 [PATCH v2 1/1] crypto/scheduler: rename slave to worker checkpatch
2020-09-28 15:55 ` [dpdk-test-report] |SUCCESS| pw79019 " 0-day Robot
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).