automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw92209 [PATCH v2 23/33] event/cnxk: add devargs to disable NPA
Date: Mon, 26 Apr 2021 19:49:24 +0200 (CEST)	[thread overview]
Message-ID: <20210426174924.EBB67121158@dpdk.org> (raw)
In-Reply-To: <20210426174441.2302-24-pbhagavatula@marvell.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#79: 
If the chunks are allocated from NPA then TIM can automatically free

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#84: 
	--dev "0002:0e:00.0,tim_disable_npa=1"

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#105: FILE: doc/guides/eventdevs/cnxk.rst:96:
+- ``TIM disable NPA``

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#107: FILE: doc/guides/eventdevs/cnxk.rst:98:
+  By default chunks are allocated from NPA then TIM can automatically free

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#108: FILE: doc/guides/eventdevs/cnxk.rst:99:
+  them when traversing the list of chunks. The ``tim_disable_npa`` devargs

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#113: FILE: doc/guides/eventdevs/cnxk.rst:104:
+    -a 0002:0e:00.0,tim_disable_npa=1

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#128: FILE: drivers/event/cnxk/cn10k_eventdev.c:506:
+			      CNXK_TIM_DISABLE_NPA "=1");

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#139: FILE: drivers/event/cnxk/cn9k_eventdev.c:575:
+			      CNXK_TIM_DISABLE_NPA "=1");

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#176: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:34:
+	if (!tim_ring->disable_npa) {

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#177: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:35:
+		tim_ring->chunk_pool = rte_mempool_create_empty(

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#178: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:36:
+			pool_name, tim_ring->nb_chunks, tim_ring->chunk_sz,

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#178: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:36:
+			pool_name, tim_ring->nb_chunks, tim_ring->chunk_sz,

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#181: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:39:
+		if (tim_ring->chunk_pool == NULL) {

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#192: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:44:
+		rc = rte_mempool_set_ops_byname(tim_ring->chunk_pool,

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#204: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:52:
+		rc = rte_mempool_populate_default(tim_ring->chunk_pool);

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#209: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:57:
+		tim_ring->aura = roc_npa_aura_handle_to_aura(

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#210: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:58:
+			tim_ring->chunk_pool->pool_id);

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#211: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:59:
+		tim_ring->ena_dfb = 0;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#213: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:61:
+		tim_ring->chunk_pool = rte_mempool_create(

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#214: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:62:
+			pool_name, tim_ring->nb_chunks, tim_ring->chunk_sz,

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#214: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:62:
+			pool_name, tim_ring->nb_chunks, tim_ring->chunk_sz,

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#217: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:65:
+		if (tim_ring->chunk_pool == NULL) {

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#221: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:69:
+		tim_ring->ena_dfb = 1;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#233: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:126:
+	tim_ring->disable_npa = dev->disable_npa;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#235: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:128:
+	if (tim_ring->disable_npa) {

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#236: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:129:
+		tim_ring->nb_chunks =

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#237: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:130:
+			tim_ring->nb_timers /

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#238: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:131:
+			CNXK_TIM_NB_CHUNK_SLOTS(tim_ring->chunk_sz);

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#238: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:131:
+			CNXK_TIM_NB_CHUNK_SLOTS(tim_ring->chunk_sz);

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#239: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:132:
+		tim_ring->nb_chunks = tim_ring->nb_chunks * tim_ring->nb_bkts;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#239: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:132:
+		tim_ring->nb_chunks = tim_ring->nb_chunks * tim_ring->nb_bkts;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#239: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:132:
+		tim_ring->nb_chunks = tim_ring->nb_chunks * tim_ring->nb_bkts;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#241: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:134:
+		tim_ring->nb_chunks = tim_ring->nb_timers;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#241: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:134:
+		tim_ring->nb_chunks = tim_ring->nb_timers;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#253: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:225:
+cnxk_tim_parse_devargs(struct rte_devargs *devargs, struct cnxk_tim_evdev *dev)

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#253: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:225:
+cnxk_tim_parse_devargs(struct rte_devargs *devargs, struct cnxk_tim_evdev *dev)

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#264: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:236:
+	rte_kvargs_process(kvlist, CNXK_TIM_DISABLE_NPA, &parse_kvargs_flag,

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#277: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:260:
+	cnxk_tim_parse_devargs(sso->pci_dev->device.devargs, dev);

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#290: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:36:
+#define CNXK_TIM_DISABLE_NPA "tim_disable_npa"

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#290: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:36:
+#define CNXK_TIM_DISABLE_NPA "tim_disable_npa"

total: 0 errors, 40 warnings, 179 lines checked

           reply	other threads:[~2021-04-26 17:49 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20210426174441.2302-24-pbhagavatula@marvell.com>]

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=20210426174924.EBB67121158@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=pbhagavatula@marvell.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).