automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-test-report] |WARNING| pw80214 [PATCH v4 03/17] eal: rename lcore word choices
Date: Fri,  9 Oct 2020 23:40:37 +0200 (CEST)	[thread overview]
Message-ID: <20201009214037.9C3E21D5A4@dpdk.org> (raw)
In-Reply-To: <20201009213855.17933-4-stephen@networkplumber.org>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#80: 
Replace master lcore with main lcore and

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#81: 
replace slave lcore with worker lcore.

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#86: 
The "--master-lcore" command line option is also deprecated

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#155: FILE: doc/guides/rel_notes/release_20_11.rst:255:
+* eal: Changed the function ``rte_get_master_lcore()`` is

WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#159: FILE: doc/guides/rel_notes/release_20_11.rst:259:
+  ``RTE_LCORE_FOREACH_SLAVE`` will be replaced with

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#162: FILE: doc/guides/rel_notes/release_20_11.rst:262:
+  The ``master-lcore`` argument to testpmd will be replaced

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#163: FILE: doc/guides/rel_notes/release_20_11.rst:263:
+  with ``main-lcore``. The old ``master-lcore`` argument

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#207: FILE: lib/librte_eal/common/eal_common_launch.c:24:
+rte_eal_wait_lcore(unsigned worker_id)

WARNING:TYPO_SPELLING: 'MASTER' may be misspelled - perhaps 'PRIMARY'?
#413: FILE: lib/librte_eal/common/eal_common_options.c:1598:
+			"Option --" OPT_MASTER_LCORE

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#630: FILE: lib/librte_eal/freebsd/eal_thread.c:34:
+rte_eal_remote_launch(int (*f)(void *), void *arg, unsigned worker_id)

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#793: FILE: lib/librte_eal/include/rte_launch.h:65:
+int rte_eal_remote_launch(lcore_function_t *f, void *arg, unsigned worker_id);

WARNING:TYPO_SPELLING: 'MASTER' may be misspelled - perhaps 'PRIMARY'?
#809: FILE: lib/librte_eal/include/rte_launch.h:77:
+#define SKIP_MASTER	RTE_DEPRECATED(SKIP_MASTER) SKIP_MAIN

WARNING:TYPO_SPELLING: 'MASTER' may be misspelled - perhaps 'PRIMARY'?
#809: FILE: lib/librte_eal/include/rte_launch.h:77:
+#define SKIP_MASTER	RTE_DEPRECATED(SKIP_MASTER) SKIP_MAIN

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#809: FILE: lib/librte_eal/include/rte_launch.h:77:
+#define SKIP_MASTER	RTE_DEPRECATED(SKIP_MASTER) SKIP_MAIN

WARNING:TYPO_SPELLING: 'MASTER' may be misspelled - perhaps 'PRIMARY'?
#810: FILE: lib/librte_eal/include/rte_launch.h:78:
+#define CALL_MASTER	RTE_DEPRECATED(CALL_MASTER) CALL_MAIN

WARNING:TYPO_SPELLING: 'MASTER' may be misspelled - perhaps 'PRIMARY'?
#810: FILE: lib/librte_eal/include/rte_launch.h:78:
+#define CALL_MASTER	RTE_DEPRECATED(CALL_MASTER) CALL_MAIN

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#810: FILE: lib/librte_eal/include/rte_launch.h:78:
+#define CALL_MASTER	RTE_DEPRECATED(CALL_MASTER) CALL_MAIN

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#881: FILE: lib/librte_eal/include/rte_launch.h:134:
+int rte_eal_wait_lcore(unsigned worker_id);

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#922: FILE: lib/librte_eal/include/rte_lcore.h:95:
+static inline unsigned int rte_get_master_lcore(void)

WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#966: FILE: lib/librte_eal/include/rte_lcore.h:244:
+#define RTE_LCORE_FOREACH_SLAVE(l)					\

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#966: FILE: lib/librte_eal/include/rte_lcore.h:244:
+#define RTE_LCORE_FOREACH_SLAVE(l)					\
+	RTE_DEPRECATED(RTE_LCORE_FOREACH_SLAVE) RTE_LCORE_FOREACH_WORKER(l)

WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#967: FILE: lib/librte_eal/include/rte_lcore.h:245:
+	RTE_DEPRECATED(RTE_LCORE_FOREACH_SLAVE) RTE_LCORE_FOREACH_WORKER(l)

total: 3 errors, 19 warnings, 1076 lines checked
ERROR: symbol rte_get_main_lcore is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
INFO: symbol rte_get_master_lcore is being removed, ensure that it has gone through the deprecation process

           reply	other threads:[~2020-10-09 21:40 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20201009213855.17933-4-stephen@networkplumber.org>]

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=20201009214037.9C3E21D5A4@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=stephen@networkplumber.org \
    --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).