From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw92219 [PATCH v2 33/33] event/cnxk: add devargs to control timer adapters
Date: Mon, 26 Apr 2021 19:49:50 +0200 (CEST) [thread overview]
Message-ID: <20210426174950.D4D6E121158@dpdk.org> (raw)
In-Reply-To: <20210426174441.2302-34-pbhagavatula@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/92219
_coding style issues_
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#80:
Add devargs to control each event timer adapter i.e. TIM rings internal
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#85:
--dev "0002:1e:00.0,tim_ring_ctl=[2-1023-1-0]"
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#103: FILE: doc/guides/eventdevs/cnxk.rst:138:
+- ``TIM ring control internal parameters``
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#105: FILE: doc/guides/eventdevs/cnxk.rst:140:
+ When using multiple TIM rings the ``tim_ring_ctl`` devargs can be used to
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#105: FILE: doc/guides/eventdevs/cnxk.rst:140:
+ When using multiple TIM rings the ``tim_ring_ctl`` devargs can be used to
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#106: FILE: doc/guides/eventdevs/cnxk.rst:141:
+ control each TIM rings internal parameters uniquely. The following dict
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#112: FILE: doc/guides/eventdevs/cnxk.rst:147:
+ -a 0002:0e:00.0,tim_ring_ctl=[2-1023-1-0]
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#135: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:169:
+ struct cnxk_tim_ctl *ring_ctl = &dev->ring_ctl_data[i];
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#137: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:171:
+ if (ring_ctl->ring == tim_ring->ring_id) {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#138: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:172:
+ tim_ring->chunk_sz =
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#141: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:175:
+ CNXK_TIM_CHUNK_ALIGNMENT) :
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#142: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:176:
+ tim_ring->chunk_sz;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#143: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:177:
+ tim_ring->enable_stats = ring_ctl->enable_stats;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#144: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:178:
+ tim_ring->disable_npa = ring_ctl->disable_npa;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#156: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:386:
+cnxk_tim_parse_ring_param(char *value, void *opaque)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#158: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:388:
+ struct cnxk_tim_evdev *dev = opaque;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#159: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:389:
+ struct cnxk_tim_ctl ring_ctl = {0};
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#161: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:391:
+ struct cnxk_tim_ctl *old_ptr;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#184: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:414:
+ sizeof(struct cnxk_tim_ctl) * dev->ring_ctl_cnt, 0);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#195: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:425:
+cnxk_tim_parse_ring_ctl_list(const char *value, void *opaque)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#210: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:440:
+ cnxk_tim_parse_ring_param(start + 1, opaque);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#221: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:451:
+cnxk_tim_parse_kvargs_dict(const char *key, const char *value, void *opaque)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#228: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:458:
+ cnxk_tim_parse_ring_ctl_list(value, opaque);
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#240: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:483:
+ rte_kvargs_process(kvlist, CNXK_TIM_RING_CTL,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#241: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:484:
+ &cnxk_tim_parse_kvargs_dict, &dev);
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#253: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:41:
+#define CNXK_TIM_RING_CTL "tim_ring_ctl"
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#253: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:41:
+#define CNXK_TIM_RING_CTL "tim_ring_ctl"
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#261: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:79:
+struct cnxk_tim_ctl {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#276: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:97:
+ struct cnxk_tim_ctl *ring_ctl_data;
total: 0 errors, 29 warnings, 165 lines checked
next parent reply other threads:[~2021-04-26 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210426174441.2302-34-pbhagavatula@marvell.com>
2021-04-26 17:49 ` checkpatch [this message]
2021-04-26 18:58 ` [dpdk-test-report] |FAILURE| pw92219 [dpdk-dev] " 0-day Robot
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=20210426174950.D4D6E121158@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).