From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: |WARNING| pw152871 [PATCH] event/cnxk: update timer arm routine
Date: Thu, 10 Apr 2025 20:07:18 +0200 (CEST) [thread overview]
Message-ID: <20250410180718.520371240EC@dpdk.org> (raw)
In-Reply-To: <20250410180544.10765-1-pbhagavatula@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/152871
_coding style issues_
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#107: FILE: drivers/event/cnxk/cnxk_tim_worker.h:136:
+cnxk_tim_bkt_wait_hbt(struct cnxk_tim_bkt *bkt)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#107: FILE: drivers/event/cnxk/cnxk_tim_worker.h:136:
+cnxk_tim_bkt_wait_hbt(struct cnxk_tim_bkt *bkt)
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#113: FILE: drivers/event/cnxk/cnxk_tim_worker.h:142:
+ " ldxr %[hbt], [%[w1]]
"
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#114: FILE: drivers/event/cnxk/cnxk_tim_worker.h:143:
+ " tbz %[hbt], 33, .Ldne%=
"
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#115: FILE: drivers/event/cnxk/cnxk_tim_worker.h:144:
+ " sevl
"
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#116: FILE: drivers/event/cnxk/cnxk_tim_worker.h:145:
+ ".Lrty%=: wfe
"
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#117: FILE: drivers/event/cnxk/cnxk_tim_worker.h:146:
+ " ldxr %[hbt], [%[w1]]
"
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#119: FILE: drivers/event/cnxk/cnxk_tim_worker.h:148:
+ ".Ldne%=:
"
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#159: FILE: drivers/event/cnxk/cnxk_tim_worker.h:295:
+ uint64_t hbt_state = cnxk_tim_bkt_wait_hbt(bkt);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#161: FILE: drivers/event/cnxk/cnxk_tim_worker.h:297:
+ if (cnxk_tim_bkt_get_nent(lock_sema) != 0 &&
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#162: FILE: drivers/event/cnxk/cnxk_tim_worker.h:298:
+ cnxk_tim_bkt_get_nent(hbt_state) == 0) {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#163: FILE: drivers/event/cnxk/cnxk_tim_worker.h:299:
+ cnxk_tim_bkt_dec_lock(bkt);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#167: FILE: drivers/event/cnxk/cnxk_tim_worker.h:303:
+ if (cnxk_tim_bkt_get_nent(hbt_state) != 0)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#176: FILE: drivers/event/cnxk/cnxk_tim_worker.h:312:
+ cnxk_tim_bkt_wait_hbt(bkt);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#185: FILE: drivers/event/cnxk/cnxk_tim_worker.h:344:
+ tim->state = RTE_EVENT_TIMER_ARMED;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#188: FILE: drivers/event/cnxk/cnxk_tim_worker.h:346:
+ cnxk_tim_bkt_dec_lock(bkt);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#215: FILE: drivers/event/cnxk/cnxk_tim_worker.h:371:
+ uint64_t hbt_state = cnxk_tim_bkt_wait_hbt(bkt);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#217: FILE: drivers/event/cnxk/cnxk_tim_worker.h:373:
+ if (cnxk_tim_bkt_get_nent(lock_sema) != 0 &&
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#218: FILE: drivers/event/cnxk/cnxk_tim_worker.h:374:
+ cnxk_tim_bkt_get_nent(hbt_state) == 0) {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#219: FILE: drivers/event/cnxk/cnxk_tim_worker.h:375:
+ cnxk_tim_bkt_dec_lock(bkt);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#223: FILE: drivers/event/cnxk/cnxk_tim_worker.h:379:
+ if (cnxk_tim_bkt_get_nent(hbt_state) != 0)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#232: FILE: drivers/event/cnxk/cnxk_tim_worker.h:388:
+ cnxk_tim_bkt_wait_hbt(bkt);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#247: FILE: drivers/event/cnxk/cnxk_tim_worker.h:434:
+ cnxk_tim_bkt_inc_nent(bkt);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#256: FILE: drivers/event/cnxk/cnxk_tim_worker.h:442:
+ cnxk_tim_bkt_inc_nent(bkt);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#265: FILE: drivers/event/cnxk/cnxk_tim_worker.h:448:
+ tim->state = RTE_EVENT_TIMER_ARMED;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#266: FILE: drivers/event/cnxk/cnxk_tim_worker.h:449:
+ cnxk_tim_bkt_dec_lock(bkt);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#293: FILE: drivers/event/cnxk/cnxk_tim_worker.h:496:
+ uint64_t hbt_state = cnxk_tim_bkt_wait_hbt(bkt);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#295: FILE: drivers/event/cnxk/cnxk_tim_worker.h:498:
+ if (cnxk_tim_bkt_get_nent(lock_sema) != 0 &&
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#296: FILE: drivers/event/cnxk/cnxk_tim_worker.h:499:
+ cnxk_tim_bkt_get_nent(hbt_state) == 0) {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#297: FILE: drivers/event/cnxk/cnxk_tim_worker.h:500:
+ cnxk_tim_bkt_dec_lock(bkt);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#301: FILE: drivers/event/cnxk/cnxk_tim_worker.h:504:
+ if (cnxk_tim_bkt_get_nent(hbt_state) != 0)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#310: FILE: drivers/event/cnxk/cnxk_tim_worker.h:513:
+ cnxk_tim_bkt_wait_hbt(bkt);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#319: FILE: drivers/event/cnxk/cnxk_tim_worker.h:562:
+ cnxk_tim_bkt_dec_lock(bkt);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#328: FILE: drivers/event/cnxk/cnxk_tim_worker.h:584:
+ cnxk_tim_bkt_dec_lock(bkt);
total: 0 errors, 34 warnings, 229 lines checked
next prev parent reply other threads:[~2025-04-10 18:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250410180544.10765-1-pbhagavatula@marvell.com>
2025-04-10 17:52 ` |SUCCESS| " qemudev
2025-04-10 17:56 ` qemudev
2025-04-10 18:07 ` checkpatch [this message]
2025-04-10 18:51 ` |PENDING| " dpdklab
2025-04-10 18:51 ` dpdklab
2025-04-10 18:52 ` dpdklab
2025-04-10 18:53 ` dpdklab
2025-04-10 18:53 ` |SUCCESS| " dpdklab
2025-04-10 18:56 ` dpdklab
2025-04-10 18:59 ` dpdklab
2025-04-10 18:59 ` |PENDING| " dpdklab
2025-04-10 19:02 ` |SUCCESS| " dpdklab
2025-04-10 19:12 ` dpdklab
2025-04-10 19:17 ` dpdklab
2025-04-10 19:20 ` dpdklab
2025-04-10 19:21 ` dpdklab
2025-04-10 19:21 ` dpdklab
2025-04-10 19:23 ` 0-day Robot
2025-04-10 19:31 ` dpdklab
2025-04-10 19:44 ` dpdklab
2025-04-10 20:24 ` dpdklab
2025-04-10 20:31 ` dpdklab
2025-04-11 21:55 ` dpdklab
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=20250410180718.520371240EC@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).