[dpdk-test-report] |WARNING| pw55486 [PATCH v3 01/14] eal: add API to lock/unlock memory hotplug

checkpatch at dpdk.org checkpatch at dpdk.org
Thu Jun 27 13:40:25 CEST 2019

Previous message: [dpdk-test-report] |WARNING| pw55484 [PATCH 9/9] enforce __rte_experimental at the start of symbol declarations
Next message: [dpdk-test-report] |SUCCESS| pw55487 [PATCH v3 02/14] drivers: use new memory locking API
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/55486

_coding style issues_


ERROR: symbol rte_mcfg_mem_read_lock is added in the DPDK_19.08 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_mcfg_mem_read_unlock is added in the DPDK_19.08 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_mcfg_mem_write_lock is added in the DPDK_19.08 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_mcfg_mem_write_unlock is added in the DPDK_19.08 section, but is expected to be added in the EXPERIMENTAL section of the version map

Previous message: [dpdk-test-report] |WARNING| pw55484 [PATCH 9/9] enforce __rte_experimental at the start of symbol declarations
Next message: [dpdk-test-report] |SUCCESS| pw55487 [PATCH v3 02/14] drivers: use new memory locking API
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the test-report mailing list