From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Sarosh Arif <sarosh.arif@emumba.com>
Subject: [dpdk-test-report] |WARNING| pw73683 [PATCH v3] lib/librte_timer:fix corruption with reset
Date: Fri, 10 Jul 2020 09:01:45 +0200 (CEST) [thread overview]
Message-ID: <20200710070145.93C701DB40@dpdk.org> (raw)
In-Reply-To: <20200710065954.4937-1-sarosh.arif@emumba.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/73683
_coding style issues_
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#122: FILE: lib/librte_timer/rte_timer.c:587:
+ if (tim->status.state == RTE_TIMER_RUNNING &&
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#123: FILE: lib/librte_timer/rte_timer.c:588:
+ (tim->status.owner != (uint16_t)tim_lcore ||
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#123: FILE: lib/librte_timer/rte_timer.c:588:
+ (tim->status.owner != (uint16_t)tim_lcore ||
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#124: FILE: lib/librte_timer/rte_timer.c:589:
+ tim != timer_data->priv_timer[tim_lcore].running_tim))
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#124: FILE: lib/librte_timer/rte_timer.c:589:
+ tim != timer_data->priv_timer[tim_lcore].running_tim))
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#124: FILE: lib/librte_timer/rte_timer.c:589:
+ tim != timer_data->priv_timer[tim_lcore].running_tim))
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#148: FILE: lib/librte_timer/rte_timer.c:663:
+ if (tim->status.state == RTE_TIMER_RUNNING &&
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#149: FILE: lib/librte_timer/rte_timer.c:664:
+ (tim->status.owner != (uint16_t)lcore_id ||
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#150: FILE: lib/librte_timer/rte_timer.c:665:
+ tim != timer_data->priv_timer[lcore_id].running_tim))
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#150: FILE: lib/librte_timer/rte_timer.c:665:
+ tim != timer_data->priv_timer[lcore_id].running_tim))
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#178: FILE: lib/librte_timer/rte_timer.h:317:
+int rte_timer_stop_sync(struct rte_timer *tim);
total: 0 errors, 11 warnings, 65 lines checked
next parent reply other threads:[~2020-07-10 7:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200710065954.4937-1-sarosh.arif@emumba.com>
2020-07-10 7:01 ` checkpatch [this message]
2020-07-10 9:55 ` [dpdk-test-report] |WARNING| pw73683 " 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=20200710070145.93C701DB40@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=sarosh.arif@emumba.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).