From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Shijith Thotton <sthotton@marvell.com>
Subject: |WARNING| pw109146 [PATCH v2 6/6] common/cnxk: use lock when accessing mbox of SSO
Date: Tue, 5 Apr 2022 07:42:42 +0200 (CEST) [thread overview]
Message-ID: <20220405054242.CD1B7122BA2@dpdk.org> (raw)
In-Reply-To: <9c22418754c23d37e29ea63ad476d8743bcb8743.1649136534.git.sthotton@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/109146
_coding style issues_
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#530: FILE: drivers/common/cnxk/roc_tim.c:11:
+ struct sso *sso = roc_sso_to_sso_priv(roc_tim->roc_sso);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#550: FILE: drivers/common/cnxk/roc_tim.c:92:
+ struct sso *sso = roc_sso_to_sso_priv(roc_tim->roc_sso);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#587: FILE: drivers/common/cnxk/roc_tim.c:124:
+ struct sso *sso = roc_sso_to_sso_priv(roc_tim->roc_sso);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#619: FILE: drivers/common/cnxk/roc_tim.c:160:
+ struct sso *sso = roc_sso_to_sso_priv(roc_tim->roc_sso);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#655: FILE: drivers/common/cnxk/roc_tim.c:197:
+ struct sso *sso = roc_sso_to_sso_priv(roc_tim->roc_sso);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#769: FILE: drivers/common/cnxk/roc_tim.c:317:
+ sso = roc_sso_to_sso_priv(roc_tim->roc_sso);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#841: FILE: drivers/common/cnxk/roc_tim.c:376:
+ struct sso *sso = roc_sso_to_sso_priv(roc_tim->roc_sso);
total: 0 errors, 7 warnings, 713 lines checked
next parent reply other threads:[~2022-04-05 5:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9c22418754c23d37e29ea63ad476d8743bcb8743.1649136534.git.sthotton@marvell.com>
2022-04-05 5:42 ` checkpatch [this message]
2022-04-05 7:39 ` |SUCCESS| " 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=20220405054242.CD1B7122BA2@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=sthotton@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).