From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: |WARNING| pw122886 [PATCH 2/2] event/cnxk: update timer arm burst parameters
Date: Thu, 2 Feb 2023 09:11:27 +0100 (CET) [thread overview]
Message-ID: <20230202081127.35FAA121E50@dpdk.org> (raw)
In-Reply-To: <20230202081025.4176-2-pbhagavatula@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/122886
_coding style issues_
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#114: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:32:
+ cache_sz = CNXK_TIM_MAX_POOL_CACHE_SZ;
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#127: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:27:
+#define CNXK_TIM_RING_DEF_CHUNK_SZ (1024)
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#131: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:29:
+#define CNXK_TIM_MAX_BURST (16)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#144: FILE: drivers/event/cnxk/cnxk_tim_worker.h:109:
+cnxk_tim_bkt_add_nent_relaxed(struct cnxk_tim_bkt *bktp, uint32_t v)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#144: FILE: drivers/event/cnxk/cnxk_tim_worker.h:109:
+cnxk_tim_bkt_add_nent_relaxed(struct cnxk_tim_bkt *bktp, uint32_t v)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#150: FILE: drivers/event/cnxk/cnxk_tim_worker.h:115:
+cnxk_tim_bkt_add_nent(struct cnxk_tim_bkt *bktp, uint32_t v)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#150: FILE: drivers/event/cnxk/cnxk_tim_worker.h:115:
+cnxk_tim_bkt_add_nent(struct cnxk_tim_bkt *bktp, uint32_t v)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#163: FILE: drivers/event/cnxk/cnxk_tim_worker.h:539:
+ cnxk_tim_bkt_add_nent_relaxed(bkt, chunk_remainder);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#172: FILE: drivers/event/cnxk/cnxk_tim_worker.h:570:
+ cnxk_tim_bkt_dec_lock_relaxed(bkt);
total: 0 errors, 9 warnings, 69 lines checked
next prev parent reply other threads:[~2023-02-02 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230202081025.4176-2-pbhagavatula@marvell.com>
2023-02-02 8:05 ` |SUCCESS| pw122885-122886 " qemudev
2023-02-02 8:09 ` qemudev
2023-02-02 8:11 ` checkpatch [this message]
2023-02-02 9:19 ` |SUCCESS| pw122886 " 0-day Robot
2023-02-02 11:56 ` |SUCCESS| pw122885-122886 " qemudev
2023-02-03 10:51 ` qemudev
2023-02-03 10:56 ` qemudev
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=20230202081127.35FAA121E50@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).