From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
Subject: |WARNING| pw122047 [PATCH v4] eventdev/timer: add API to get remaining ticks
Date: Fri, 13 Jan 2023 20:51:31 +0100 (CET) [thread overview]
Message-ID: <20230113195131.E3C57123659@dpdk.org> (raw)
In-Reply-To: <20230113195021.1747261-1-erik.g.carrillo@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/122047
_coding style issues_
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#104: FILE: app/test/test_event_timer_adapter.c:1927:
+ struct rte_event_timer *ev_tim;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#107: FILE: app/test/test_event_timer_adapter.c:1930:
+ const struct rte_event_timer tim = {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#116: 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'?
#117: FILE: app/test/test_event_timer_adapter.c:1940:
+ *ev_tim = tim;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#117: FILE: app/test/test_event_timer_adapter.c:1940:
+ *ev_tim = tim;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#118: 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'?
#118: 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'?
#120: 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'?
#122: FILE: app/test/test_event_timer_adapter.c:1945:
+ ret = rte_event_timer_remaining_ticks_get(timdev, ev_tim,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#125: FILE: app/test/test_event_timer_adapter.c:1948:
+ rte_mempool_put(eventdev_test_mempool, (void *)ev_tim);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#134: FILE: app/test/test_event_timer_adapter.c:1957:
+ TEST_ASSERT_EQUAL(rte_event_timer_arm_burst(timdev, &ev_tim, 1), 1,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#136: FILE: app/test/test_event_timer_adapter.c:1959:
+ TEST_ASSERT_EQUAL(ev_tim->state, RTE_EVENT_TIMER_ARMED,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#138: FILE: app/test/test_event_timer_adapter.c:1961:
+ RTE_EVENT_TIMER_ARMED, ev_tim->state);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#141: FILE: app/test/test_event_timer_adapter.c:1964:
+ ret = rte_event_timer_remaining_ticks_get(timdev, ev_tim,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#157: FILE: app/test/test_event_timer_adapter.c:1980:
+ TEST_ASSERT_EQUAL(ev_tim->state, RTE_EVENT_TIMER_NOT_ARMED,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#159: FILE: app/test/test_event_timer_adapter.c:1982:
+ RTE_EVENT_TIMER_NOT_ARMED, ev_tim->state);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#162: FILE: app/test/test_event_timer_adapter.c:1985:
+ TEST_ASSERT_FAIL(rte_event_timer_remaining_ticks_get(timdev, ev_tim,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#166: FILE: app/test/test_event_timer_adapter.c:1989:
+ rte_mempool_put(eventdev_test_mempool, (void *)ev_tim);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#257: FILE: lib/eventdev/rte_event_timer_adapter.c:1100:
+ struct rte_timer *tim;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#266: FILE: lib/eventdev/rte_event_timer_adapter.c:1109:
+ tim = (struct rte_timer *)(uintptr_t)opaque;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#269: FILE: lib/eventdev/rte_event_timer_adapter.c:1112:
+ if (cur_cycles > tim->expire) {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#274: FILE: lib/eventdev/rte_event_timer_adapter.c:1117:
+ cycles_remaining = tim->expire - cur_cycles;
total: 0 errors, 22 warnings, 225 lines checked
next prev parent reply other threads:[~2023-01-13 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230113195021.1747261-1-erik.g.carrillo@intel.com>
2023-01-13 19:43 ` |SUCCESS| " qemudev
2023-01-13 19:47 ` qemudev
2023-01-13 19:51 ` checkpatch [this message]
2023-01-13 20:39 ` 0-day Robot
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=20230113195131.E3C57123659@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).