From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Shijith Thotton <sthotton@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw89088 [PATCH v2 2/3] test/event: add unit tests for periodic timer
Date: Sun, 14 Mar 2021 17:46:42 +0100 (CET) [thread overview]
Message-ID: <20210314164642.618F02A62@dpdk.org> (raw)
In-Reply-To: <c006e106bad755e1a87bb411d9e2127a59b3f968.1615738894.git.sthotton@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/89088
_coding style issues_
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#212: FILE: app/test/test_event_timer_adapter.c:559:
+ * there will be 10 * MAX_TIMERS periodic timer triggers */
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#231: FILE: app/test/test_event_timer_adapter.c:646:
+ * there will be 10 * MAX_TIMERS periodic timer triggers */
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#249: FILE: app/test/test_event_timer_adapter.c:681:
+ struct rte_event_timer *ev_tim;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#250: FILE: app/test/test_event_timer_adapter.c:682:
+ const struct rte_event_timer tim = {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#262: FILE: app/test/test_event_timer_adapter.c:694:
+ (void **)&ev_tim),
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#264: FILE: app/test/test_event_timer_adapter.c:696:
+ *ev_tim = tim;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#264: FILE: app/test/test_event_timer_adapter.c:696:
+ *ev_tim = tim;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#265: FILE: app/test/test_event_timer_adapter.c:697:
+ ev_tim->ev.event_ptr = ev_tim;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#265: FILE: app/test/test_event_timer_adapter.c:697:
+ ev_tim->ev.event_ptr = ev_tim;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#267: FILE: app/test/test_event_timer_adapter.c:699:
+ TEST_ASSERT_EQUAL(rte_event_timer_arm_burst(timdev, &ev_tim,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#274: FILE: app/test/test_event_timer_adapter.c:706:
+ &ev_tim, 1), 1,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#276: FILE: app/test/test_event_timer_adapter.c:708:
+ rte_mempool_put(eventdev_test_mempool, ev_tim);
total: 0 errors, 12 warnings, 222 lines checked
parent reply other threads:[~2021-03-14 16:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <c006e106bad755e1a87bb411d9e2127a59b3f968.1615738894.git.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=20210314164642.618F02A62@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).