From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw88671 [PATCH 29/36] event/cnxk: add timer cancel function
Date: Sat, 6 Mar 2021 17:35:44 +0100 (CET) [thread overview]
Message-ID: <20210306163544.D68A42B9D@dpdk.org> (raw)
In-Reply-To: <20210306162942.6845-30-pbhagavatula@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/88671
_coding style issues_
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#98: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:99:
+ cnxk_tim_ops.cancel_burst = cnxk_tim_timer_cancel_burst;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#98: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:99:
+ cnxk_tim_ops.cancel_burst = cnxk_tim_timer_cancel_burst;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#111: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:240:
+cnxk_tim_timer_cancel_burst(const struct rte_event_timer_adapter *adptr,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#112: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:241:
+ struct rte_event_timer **tim,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#128: FILE: drivers/event/cnxk/cnxk_tim_worker.c:157:
+cnxk_tim_timer_cancel_burst(const struct rte_event_timer_adapter *adptr,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#129: FILE: drivers/event/cnxk/cnxk_tim_worker.c:158:
+ struct rte_event_timer **tim,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#138: FILE: drivers/event/cnxk/cnxk_tim_worker.c:167:
+ if (tim[index]->state == RTE_EVENT_TIMER_CANCELED) {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#143: FILE: drivers/event/cnxk/cnxk_tim_worker.c:172:
+ if (tim[index]->state != RTE_EVENT_TIMER_ARMED) {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#147: FILE: drivers/event/cnxk/cnxk_tim_worker.c:176:
+ ret = cnxk_tim_rm_entry(tim[index]);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#147: FILE: drivers/event/cnxk/cnxk_tim_worker.c:176:
+ ret = cnxk_tim_rm_entry(tim[index]);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#165: FILE: drivers/event/cnxk/cnxk_tim_worker.h:565:
+cnxk_tim_rm_entry(struct rte_event_timer *tim)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#165: FILE: drivers/event/cnxk/cnxk_tim_worker.h:565:
+cnxk_tim_rm_entry(struct rte_event_timer *tim)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#167: FILE: drivers/event/cnxk/cnxk_tim_worker.h:567:
+ struct cnxk_tim_ent *entry;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#168: FILE: drivers/event/cnxk/cnxk_tim_worker.h:568:
+ struct cnxk_tim_bkt *bkt;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#171: FILE: drivers/event/cnxk/cnxk_tim_worker.h:571:
+ if (tim->impl_opaque[1] == 0 || tim->impl_opaque[0] == 0)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#171: FILE: drivers/event/cnxk/cnxk_tim_worker.h:571:
+ if (tim->impl_opaque[1] == 0 || tim->impl_opaque[0] == 0)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#174: FILE: drivers/event/cnxk/cnxk_tim_worker.h:574:
+ entry = (struct cnxk_tim_ent *)(uintptr_t)tim->impl_opaque[0];
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#174: FILE: drivers/event/cnxk/cnxk_tim_worker.h:574:
+ entry = (struct cnxk_tim_ent *)(uintptr_t)tim->impl_opaque[0];
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#175: FILE: drivers/event/cnxk/cnxk_tim_worker.h:575:
+ if (entry->wqe != tim->ev.u64) {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#176: FILE: drivers/event/cnxk/cnxk_tim_worker.h:576:
+ tim->impl_opaque[0] = 0;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#177: FILE: drivers/event/cnxk/cnxk_tim_worker.h:577:
+ tim->impl_opaque[1] = 0;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#181: FILE: drivers/event/cnxk/cnxk_tim_worker.h:581:
+ bkt = (struct cnxk_tim_bkt *)(uintptr_t)tim->impl_opaque[1];
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#181: FILE: drivers/event/cnxk/cnxk_tim_worker.h:581:
+ bkt = (struct cnxk_tim_bkt *)(uintptr_t)tim->impl_opaque[1];
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#182: FILE: drivers/event/cnxk/cnxk_tim_worker.h:582:
+ lock_sema = cnxk_tim_bkt_inc_lock(bkt);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#183: FILE: drivers/event/cnxk/cnxk_tim_worker.h:583:
+ if (cnxk_tim_bkt_get_hbt(lock_sema) ||
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#184: FILE: drivers/event/cnxk/cnxk_tim_worker.h:584:
+ !cnxk_tim_bkt_get_nent(lock_sema)) {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#185: FILE: drivers/event/cnxk/cnxk_tim_worker.h:585:
+ tim->impl_opaque[0] = 0;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#186: FILE: drivers/event/cnxk/cnxk_tim_worker.h:586:
+ tim->impl_opaque[1] = 0;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#187: FILE: drivers/event/cnxk/cnxk_tim_worker.h:587:
+ cnxk_tim_bkt_dec_lock(bkt);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#193: FILE: drivers/event/cnxk/cnxk_tim_worker.h:593:
+ tim->state = RTE_EVENT_TIMER_CANCELED;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#194: FILE: drivers/event/cnxk/cnxk_tim_worker.h:594:
+ tim->impl_opaque[0] = 0;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#195: FILE: drivers/event/cnxk/cnxk_tim_worker.h:595:
+ tim->impl_opaque[1] = 0;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#196: FILE: drivers/event/cnxk/cnxk_tim_worker.h:596:
+ cnxk_tim_bkt_dec_lock(bkt);
total: 0 errors, 33 warnings, 92 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-30-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=20210306163544.D68A42B9D@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).