From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw92206 [PATCH v2 20/33] event/cnxk: support event timer
Date: Mon, 26 Apr 2021 19:49:17 +0200 (CEST) [thread overview]
Message-ID: <20210426174917.C142D121158@dpdk.org> (raw)
In-Reply-To: <20210426174441.2302-21-pbhagavatula@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/92206
_coding style issues_
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#80:
Add event timer adapter aka TIM initialization on SSO probe.
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#103: FILE: doc/guides/eventdevs/cnxk.rst:38:
+- HW managed event timers support through TIM, with high precision and
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#105: FILE: doc/guides/eventdevs/cnxk.rst:40:
+- Up to 256 TIM rings aka event timer adapters.
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#114: FILE: doc/guides/eventdevs/cnxk.rst:108:
+ | 2 | TIM | --log-level='pmd\.event\.cnxk\.timer,8' |
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#124: FILE: drivers/event/cnxk/cnxk_eventdev.c:585:
+ cnxk_tim_init(&dev->sso);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#133: FILE: drivers/event/cnxk/cnxk_eventdev.c:603:
+ cnxk_tim_fini();
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#145: FILE: drivers/event/cnxk/cnxk_eventdev.h:17:
+#include "cnxk_tim_evdev.h"
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#161: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:6:
+#include "cnxk_tim_evdev.h"
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#164: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:9:
+cnxk_tim_init(struct roc_sso *sso)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#167: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:12:
+ struct cnxk_tim_evdev *dev;
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#173: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:18:
+ mz = rte_memzone_reserve(RTE_STR(CNXK_TIM_EVDEV_NAME),
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#174: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:19:
+ sizeof(struct cnxk_tim_evdev), 0, 0);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#176: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:21:
+ plt_tim_dbg("Unable to allocate memory for TIM Event device");
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#176: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:21:
+ plt_tim_dbg("Unable to allocate memory for TIM Event device");
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#181: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:26:
+ dev->tim.roc_sso = sso;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#182: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:27:
+ rc = roc_tim_init(&dev->tim);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#182: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:27:
+ rc = roc_tim_init(&dev->tim);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#184: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:29:
+ plt_err("Failed to initialize roc tim resources");
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#189: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:34:
+ dev->chunk_sz = CNXK_TIM_RING_DEF_CHUNK_SZ;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#193: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:38:
+cnxk_tim_fini(void)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#195: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:40:
+ struct cnxk_tim_evdev *dev = tim_priv_get();
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#195: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:40:
+ struct cnxk_tim_evdev *dev = tim_priv_get();
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#200: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:45:
+ roc_tim_fini(&dev->tim);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#200: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:45:
+ roc_tim_fini(&dev->tim);
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#201: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:46:
+ rte_memzone_free(rte_memzone_lookup(RTE_STR(CNXK_TIM_EVDEV_NAME)));
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#213: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:5:
+#ifndef __CNXK_TIM_EVDEV_H__
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#214: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:6:
+#define __CNXK_TIM_EVDEV_H__
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#227: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:19:
+#define CNXK_TIM_EVDEV_NAME cnxk_tim_eventdev
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#227: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:19:
+#define CNXK_TIM_EVDEV_NAME cnxk_tim_eventdev
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#228: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:20:
+#define CNXK_TIM_RING_DEF_CHUNK_SZ (4096)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#230: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:22:
+struct cnxk_tim_evdev {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#231: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:23:
+ struct roc_tim tim;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#231: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:23:
+ struct roc_tim tim;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#237: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:29:
+static inline struct cnxk_tim_evdev *
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#238: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:30:
+tim_priv_get(void)
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#242: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:34:
+ mz = rte_memzone_lookup(RTE_STR(CNXK_TIM_EVDEV_NAME));
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#249: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:41:
+void cnxk_tim_init(struct roc_sso *sso);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#250: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:42:
+void cnxk_tim_fini(void);
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#252: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:44:
+#endif /* __CNXK_TIM_EVDEV_H__ */
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#261: FILE: drivers/event/cnxk/meson.build:18:
+ 'cnxk_tim_evdev.c',
total: 0 errors, 40 warnings, 136 lines checked
parent reply other threads:[~2021-04-26 17:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210426174441.2302-21-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=20210426174917.C142D121158@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).