From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw88667 [PATCH 25/36] event/cnxk: add devargs for chunk size and rings
Date: Sat, 6 Mar 2021 17:35:32 +0100 (CET) [thread overview]
Message-ID: <20210306163532.1BFE12B9D@dpdk.org> (raw)
In-Reply-To: <20210306162942.6845-26-pbhagavatula@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/88667
_coding style issues_
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#84:
--dev "0002:1e:00.0,tim_chnk_slots=1024"
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#85:
--dev "0002:1e:00.0,tim_rings_lmt=4"
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#105: FILE: doc/guides/eventdevs/cnxk.rst:106:
+- ``TIM modify chunk slots``
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#107: FILE: doc/guides/eventdevs/cnxk.rst:108:
+ The ``tim_chnk_slots`` devargs can be used to modify number of chunk slots.
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#110: FILE: doc/guides/eventdevs/cnxk.rst:111:
+ store events. TIM traverses the list of chunks and enqueues the event timers
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#115: FILE: doc/guides/eventdevs/cnxk.rst:116:
+ -a 0002:0e:00.0,tim_chnk_slots=1023
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#117: FILE: doc/guides/eventdevs/cnxk.rst:118:
+- ``TIM limit max rings reserved``
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#119: FILE: doc/guides/eventdevs/cnxk.rst:120:
+ The ``tim_rings_lmt`` devargs can be used to limit the max number of TIM
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#119: FILE: doc/guides/eventdevs/cnxk.rst:120:
+ The ``tim_rings_lmt`` devargs can be used to limit the max number of TIM
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#120: FILE: doc/guides/eventdevs/cnxk.rst:121:
+ rings i.e. event timer adapter reserved on probe. Since, TIM rings are HW
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#126: FILE: doc/guides/eventdevs/cnxk.rst:127:
+ -a 0002:0e:00.0,tim_rings_lmt=5
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#140: FILE: drivers/event/cnxk/cn10k_eventdev.c:506:
+ CNXK_TIM_DISABLE_NPA "=1"
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#141: FILE: drivers/event/cnxk/cn10k_eventdev.c:507:
+ CNXK_TIM_CHNK_SLOTS "=<int>"
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#142: FILE: drivers/event/cnxk/cn10k_eventdev.c:508:
+ CNXK_TIM_RINGS_LMT "=<int>");
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#152: FILE: drivers/event/cnxk/cn9k_eventdev.c:575:
+ CNXK_TIM_DISABLE_NPA "=1"
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#153: FILE: drivers/event/cnxk/cn9k_eventdev.c:576:
+ CNXK_TIM_CHNK_SLOTS "=<int>"
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#154: FILE: drivers/event/cnxk/cn9k_eventdev.c:577:
+ CNXK_TIM_RINGS_LMT "=<int>");
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#163: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:256:
+ rte_kvargs_process(kvlist, CNXK_TIM_CHNK_SLOTS, &parse_kvargs_value,
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#165: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:258:
+ rte_kvargs_process(kvlist, CNXK_TIM_RINGS_LMT, &parse_kvargs_value,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#174: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:285:
+ dev->tim.nb_lfs = dev->min_ring_cnt;
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#184: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:294:
+ if (dev->chunk_slots && dev->chunk_slots <= CNXK_TIM_MAX_CHUNK_SLOTS &&
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#185: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:295:
+ dev->chunk_slots >= CNXK_TIM_MIN_CHUNK_SLOTS) {
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#187: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:297:
+ (dev->chunk_slots + 1) * CNXK_TIM_CHUNK_ALIGNMENT;
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#189: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:299:
+ dev->chunk_sz = CNXK_TIM_RING_DEF_CHUNK_SZ;
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#202: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:37:
+#define CNXK_TIM_CHNK_SLOTS "tim_chnk_slots"
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#202: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:37:
+#define CNXK_TIM_CHNK_SLOTS "tim_chnk_slots"
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#203: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:38:
+#define CNXK_TIM_RINGS_LMT "tim_rings_lmt"
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#203: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:38:
+#define CNXK_TIM_RINGS_LMT "tim_rings_lmt"
total: 0 errors, 28 warnings, 91 lines checked
parent reply other threads:[~2021-03-06 16:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210306162942.6845-26-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=20210306163532.1BFE12B9D@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).