From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Nagadheeraj Rottela <rnagadheeraj@marvell.com>
Subject: |WARNING| pw133508 [PATCH 3/7] common/nitrox: add compress hardware queue management
Date: Fri, 27 Oct 2023 16:56:41 +0200 (CEST) [thread overview]
Message-ID: <20231027145641.7A75F120A1D@dpdk.org> (raw)
In-Reply-To: <20231027145534.16803-4-rnagadheeraj@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/133508
_coding style issues_
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#99: FILE: drivers/common/nitrox/nitrox_csr.h:36:
+#define ZQMQ_TIM_LDX(_i) (0x30038UL + ((_i) * 0x40000UL))
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#167: FILE: drivers/common/nitrox/nitrox_hal.c:213:
+ union zqmq_tim_ld zqmq_tim_ld;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#167: FILE: drivers/common/nitrox/nitrox_hal.c:213:
+ union zqmq_tim_ld zqmq_tim_ld;
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#207: FILE: drivers/common/nitrox/nitrox_hal.c:253:
+ reg_addr = ZQMQ_TIM_LDX(ring);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#208: FILE: drivers/common/nitrox/nitrox_hal.c:254:
+ zqmq_tim_ld.u64 = 0;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#209: FILE: drivers/common/nitrox/nitrox_hal.c:255:
+ zqmq_tim_ld.s.timer_load_value = 0;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#210: FILE: drivers/common/nitrox/nitrox_hal.c:256:
+ nitrox_write_csr(bar_addr, reg_addr, zqmq_tim_ld.u64);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#330: FILE: drivers/common/nitrox/nitrox_hal.h:231:
+union zqmq_tim_ld {
total: 0 errors, 8 warnings, 427 lines checked
Warning in drivers/common/nitrox/nitrox_qp.h:
Using rte_atomicNN_xxx
Warning in drivers/common/nitrox/nitrox_qp.h:
Using rte_smp_[r/w]mb
parent reply other threads:[~2023-10-27 14:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20231027145534.16803-4-rnagadheeraj@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=20231027145641.7A75F120A1D@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=rnagadheeraj@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).