From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: |WARNING| pw126891 [PATCH] event/cnxk: add get remaining ticks routine
Date: Tue, 16 May 2023 16:49:00 +0200 (CEST) [thread overview]
Message-ID: <20230516144900.1B2E5120565@dpdk.org> (raw)
In-Reply-To: <20230516144824.6732-1-pbhagavatula@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/126891
_coding style issues_
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#108: FILE: drivers/event/cnxk/cn10k_worker.h:219:
+ struct rte_event_timer *tim = (void *)u64[1];
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#110: FILE: drivers/event/cnxk/cn10k_worker.h:221:
+ tim->state = RTE_EVENT_TIMER_NOT_ARMED;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#123: FILE: drivers/event/cnxk/cn9k_worker.h:219:
+ struct rte_event_timer *tim = (void *)u64[1];
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#125: FILE: drivers/event/cnxk/cn9k_worker.h:221:
+ tim->state = RTE_EVENT_TIMER_NOT_ARMED;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#137: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:395:
+ cnxk_tim_ops.remaining_ticks_get = cnxk_tim_remaining_ticks_get;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#137: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:395:
+ cnxk_tim_ops.remaining_ticks_get = cnxk_tim_remaining_ticks_get;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#149: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:323:
+int cnxk_tim_remaining_ticks_get(const struct rte_event_timer_adapter *adapter,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#165: FILE: drivers/event/cnxk/cnxk_tim_worker.c:176:
+cnxk_tim_remaining_ticks_get(const struct rte_event_timer_adapter *adapter,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#168: FILE: drivers/event/cnxk/cnxk_tim_worker.c:179:
+ struct cnxk_tim_ring *tim_ring = adapter->data->adapter_priv;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#168: FILE: drivers/event/cnxk/cnxk_tim_worker.c:179:
+ struct cnxk_tim_ring *tim_ring = adapter->data->adapter_priv;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#169: FILE: drivers/event/cnxk/cnxk_tim_worker.c:180:
+ struct cnxk_tim_bkt *bkt, *current_bkt;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#170: FILE: drivers/event/cnxk/cnxk_tim_worker.c:181:
+ struct cnxk_tim_ent *entry;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#177: FILE: drivers/event/cnxk/cnxk_tim_worker.c:188:
+ entry = (struct cnxk_tim_ent *)(uintptr_t)evtim->impl_opaque[0];
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#184: FILE: drivers/event/cnxk/cnxk_tim_worker.c:195:
+ bkt = (struct cnxk_tim_bkt *)evtim->impl_opaque[1];
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#186: FILE: drivers/event/cnxk/cnxk_tim_worker.c:197:
+ if (cnxk_tim_bkt_get_hbt(sema) || !cnxk_tim_bkt_get_nent(sema))
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#186: FILE: drivers/event/cnxk/cnxk_tim_worker.c:197:
+ if (cnxk_tim_bkt_get_hbt(sema) || !cnxk_tim_bkt_get_nent(sema))
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#189: FILE: drivers/event/cnxk/cnxk_tim_worker.c:200:
+ bkt_cyc = tim_ring->tick_fn(tim_ring->tbase) - tim_ring->ring_start_cyc;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#189: FILE: drivers/event/cnxk/cnxk_tim_worker.c:200:
+ bkt_cyc = tim_ring->tick_fn(tim_ring->tbase) - tim_ring->ring_start_cyc;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#189: FILE: drivers/event/cnxk/cnxk_tim_worker.c:200:
+ bkt_cyc = tim_ring->tick_fn(tim_ring->tbase) - tim_ring->ring_start_cyc;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#190: FILE: drivers/event/cnxk/cnxk_tim_worker.c:201:
+ bucket = rte_reciprocal_divide_u64(bkt_cyc, &tim_ring->fast_div);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#191: FILE: drivers/event/cnxk/cnxk_tim_worker.c:202:
+ current_bkt = &tim_ring->bkt[bucket];
total: 0 errors, 21 warnings, 83 lines checked
next parent reply other threads:[~2023-05-16 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230516144824.6732-1-pbhagavatula@marvell.com>
2023-05-16 14:49 ` checkpatch [this message]
2023-05-16 16:00 ` |FAILURE| " 0-day Robot
2023-05-17 3:08 ` |SUCCESS| " qemudev
2023-05-17 3:08 ` qemudev
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=20230516144900.1B2E5120565@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).