From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Nithin Dabilpuram <ndabilpuram@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw90419 [PATCH v3 46/52] common/cnxk: add sso hws interface
Date: Thu, 1 Apr 2021 14:46:20 +0200 (CEST) [thread overview]
Message-ID: <20210401124620.EA483121321@dpdk.org> (raw)
In-Reply-To: <20210401123817.14348-47-ndabilpuram@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/90419
_coding style issues_
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#148: FILE: drivers/common/cnxk/roc_sso.c:205:
+ current_us = plt_read64(base + SSOW_LF_GWS_NW_TIM);
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#150: FILE: drivers/common/cnxk/roc_sso.c:207:
+ * The SSOW_LF_GWS_NW_TIM[NW_TIM] period is specified in n-1 notation.
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#150: FILE: drivers/common/cnxk/roc_sso.c:207:
+ * The SSOW_LF_GWS_NW_TIM[NW_TIM] period is specified in n-1 notation.
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#155: FILE: drivers/common/cnxk/roc_sso.c:212:
+ * SSOW_LF_GWS_NW_TIM[NW_TIM] specifies the minimum timeout. The SSO
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#155: FILE: drivers/common/cnxk/roc_sso.c:212:
+ * SSOW_LF_GWS_NW_TIM[NW_TIM] specifies the minimum timeout. The SSO
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#157: FILE: drivers/common/cnxk/roc_sso.c:214:
+ * timeout specified by SSOW_LF_GWS_NW_TIM[NW_TIM].
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#157: FILE: drivers/common/cnxk/roc_sso.c:214:
+ * timeout specified by SSOW_LF_GWS_NW_TIM[NW_TIM].
total: 0 errors, 7 warnings, 183 lines checked
parent reply other threads:[~2021-04-01 12:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210401123817.14348-47-ndabilpuram@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=20210401124620.EA483121321@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ndabilpuram@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).