|WARNING| pw135872 [PATCH] eal: refactor rte_eal_init into sub-functions

checkpatch at dpdk.org checkpatch at dpdk.org
Mon Jan 15 09:51:31 CET 2024


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

_coding style issues_


WARNING:TYPO_SPELLING: 'dont' may be misspelled - perhaps 'don't'?
#130: FILE: app/test-pmd/testpmd.c:4569:
+	 * if testpmd application dont want to know progress/status of

WARNING:TYPO_SPELLING: 'MASTER' may be misspelled - perhaps 'PRIMARY'?
#153: FILE: lib/eal/include/rte_eal.h:117:
+ * Its called from rte_eal_init() on MASTER lcore only and must NOT be directly

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#166: FILE: lib/eal/include/rte_eal.h:130:
+ * Launched on next available slave lcore.

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#180: FILE: lib/eal/include/rte_eal.h:144:
+ * it performs all device independent operation (like mbuf pool creation) on master lcore.

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#268: FILE: lib/eal/linux/eal.c:1363:
+	int fctret = rte_eal_init_setup(argc, argv);	/* master lcore*/

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#274: FILE: lib/eal/linux/eal.c:1369:
+	/* running on a slave lcore */

total: 0 errors, 6 warnings, 169 lines checked
Warning in lib/eal/include/rte_eal.h:
Using compiler attribute directly
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
Please only put __rte_experimental tags in headers (b/lib/eal/linux/eal.c)
Please only put __rte_experimental tags in headers (b/lib/eal/linux/eal.c)
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
Please only put __rte_experimental tags in headers (b/lib/eal/linux/eal.c)
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
Please only put __rte_experimental tags in headers (b/lib/eal/linux/eal.c)
__rte_experimental must appear alone on the line immediately preceding the return type of a function.


More information about the test-report mailing list