From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Shijith Thotton <sthotton@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw87882 [RFC PATCH] eventdev: use shared memory to store timer adapter
Date: Tue, 16 Feb 2021 10:37:23 +0100 (CET) [thread overview]
Message-ID: <20210216093723.BCD22C906@dpdk.org> (raw)
In-Reply-To: <20210212101343.689792-1-sthotton@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/87882
_coding style issues_
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#244: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:65:
+ struct otx2_tim_ring *tim_ring = adptr->data.adapter_priv;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#244: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:65:
+ struct otx2_tim_ring *tim_ring = adptr->data.adapter_priv;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#283: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:293:
+ adptr->data.adapter_priv = tim_ring;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#288: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:297:
+ tim_ring->ring_id = adptr->data.id;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#306: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:429:
+ struct otx2_tim_ring *tim_ring = adptr->data.adapter_priv;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#306: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:429:
+ struct otx2_tim_ring *tim_ring = adptr->data.adapter_priv;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#315: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:472:
+ struct otx2_tim_ring *tim_ring = adptr->data.adapter_priv;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#315: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:472:
+ struct otx2_tim_ring *tim_ring = adptr->data.adapter_priv;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#324: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:495:
+ struct otx2_tim_ring *tim_ring = adptr->data.adapter_priv;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#324: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:495:
+ struct otx2_tim_ring *tim_ring = adptr->data.adapter_priv;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#342: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:525:
+ struct otx2_tim_ring *tim_ring = adapter->data.adapter_priv;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#342: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:525:
+ struct otx2_tim_ring *tim_ring = adapter->data.adapter_priv;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#351: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:540:
+ struct otx2_tim_ring *tim_ring = adapter->data.adapter_priv;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#351: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:540:
+ struct otx2_tim_ring *tim_ring = adapter->data.adapter_priv;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#364: FILE: drivers/event/octeontx2/otx2_tim_worker.c:64:
+ struct otx2_tim_ring *tim_ring = adptr->data.adapter_priv;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#364: FILE: drivers/event/octeontx2/otx2_tim_worker.c:64:
+ struct otx2_tim_ring *tim_ring = adptr->data.adapter_priv;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#373: FILE: drivers/event/octeontx2/otx2_tim_worker.c:103:
+ struct otx2_tim_ring *tim_ring = adptr->data.adapter_priv;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#373: FILE: drivers/event/octeontx2/otx2_tim_worker.c:103:
+ struct otx2_tim_ring *tim_ring = adptr->data.adapter_priv;
WARNING:MACRO_WITH_FLOW_CONTROL: Macros with flow control statements should be avoided
#931: FILE: lib/librte_eventdev/rte_event_timer_adapter.h:551:
+#define ADAPTER_VALID_OR_ERR_RET(adapter, retval) do { \
+ if (adapter == NULL) { \
+ return retval; \
+ } else { \
+ int i; \
+ for (i = 0; i < RTE_EVENT_TIMER_ADAPTER_NUM_MAX; i++) { \
+ if (adapters[i] == adapter) \
+ break; \
+ } \
+ if (i == RTE_EVENT_TIMER_ADAPTER_NUM_MAX) \
+ return retval; \
+ } \
} while (0)
total: 0 errors, 19 warnings, 815 lines checked
parent reply other threads:[~2021-02-16 9:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210212101343.689792-1-sthotton@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=20210216093723.BCD22C906@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=sthotton@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).