From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
Subject: |WARNING| pw121038 [PATCH v2] eventdev/timer: add API to get remaining ticks
Date: Mon, 19 Dec 2022 20:59:19 +0100 (CET) [thread overview]
Message-ID: <20221219195919.DA825122E70@dpdk.org> (raw)
In-Reply-To: <20221219195900.2389529-1-erik.g.carrillo@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/121038
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#93: FILE: app/test/test_event_timer_adapter.c:1927:
+ struct rte_event_timer *ev_tim;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#96: FILE: app/test/test_event_timer_adapter.c:1930:
+ const struct rte_event_timer tim = {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#105: FILE: app/test/test_event_timer_adapter.c:1939:
+ rte_mempool_get(eventdev_test_mempool, (void **)&ev_tim);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#106: FILE: app/test/test_event_timer_adapter.c:1940:
+ *ev_tim = tim;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#106: FILE: app/test/test_event_timer_adapter.c:1940:
+ *ev_tim = tim;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#107: FILE: app/test/test_event_timer_adapter.c:1941:
+ ev_tim->ev.event_ptr = ev_tim;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#107: FILE: app/test/test_event_timer_adapter.c:1941:
+ ev_tim->ev.event_ptr = ev_tim;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#109: FILE: app/test/test_event_timer_adapter.c:1943:
+ ev_tim->timeout_ticks = CALC_TICKS(TEST_TICKS);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#112: FILE: app/test/test_event_timer_adapter.c:1946:
+ TEST_ASSERT_FAIL(rte_event_timer_get_remaining_ticks(timdev, ev_tim,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#116: FILE: app/test/test_event_timer_adapter.c:1950:
+ TEST_ASSERT_EQUAL(rte_event_timer_arm_burst(timdev, &ev_tim, 1), 1,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#118: FILE: app/test/test_event_timer_adapter.c:1952:
+ TEST_ASSERT_EQUAL(ev_tim->state, RTE_EVENT_TIMER_ARMED,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#120: FILE: app/test/test_event_timer_adapter.c:1954:
+ RTE_EVENT_TIMER_ARMED, ev_tim->state);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#123: FILE: app/test/test_event_timer_adapter.c:1957:
+ ret = rte_event_timer_get_remaining_ticks(timdev, ev_tim,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#139: FILE: app/test/test_event_timer_adapter.c:1973:
+ TEST_ASSERT_EQUAL(ev_tim->state, RTE_EVENT_TIMER_NOT_ARMED,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#141: FILE: app/test/test_event_timer_adapter.c:1975:
+ RTE_EVENT_TIMER_NOT_ARMED, ev_tim->state);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#144: FILE: app/test/test_event_timer_adapter.c:1978:
+ TEST_ASSERT_FAIL(rte_event_timer_get_remaining_ticks(timdev, ev_tim,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#148: FILE: app/test/test_event_timer_adapter.c:1982:
+ rte_mempool_put(eventdev_test_mempool, (void *)ev_tim);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#238: FILE: lib/eventdev/rte_event_timer_adapter.c:1099:
+ struct rte_timer *tim;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#247: FILE: lib/eventdev/rte_event_timer_adapter.c:1108:
+ tim = (struct rte_timer *)(uintptr_t)opaque;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#250: FILE: lib/eventdev/rte_event_timer_adapter.c:1111:
+ if (cur_cycles > tim->expire) {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#255: FILE: lib/eventdev/rte_event_timer_adapter.c:1116:
+ cycles_remaining = tim->expire - cur_cycles;
total: 0 errors, 21 warnings, 217 lines checked
prev parent reply other threads:[~2022-12-19 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221219195900.2389529-1-erik.g.carrillo@intel.com>
2022-12-19 19:51 ` |SUCCESS| " qemudev
2022-12-19 19:55 ` qemudev
2022-12-19 19:59 ` checkpatch [this message]
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=20221219195919.DA825122E70@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=erik.g.carrillo@intel.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).