From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: |WARNING| pw142835 [PATCH 15/17] bus/dpaa: add ONIC port mode for the DPAA eth
Date: Thu, 1 Aug 2024 12:55:50 +0200 (CEST) [thread overview]
Message-ID: <20240801105550.D9BFD123EF2@dpdk.org> (raw)
In-Reply-To: <20240801105313.630280-16-hemant.agrawal@nxp.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/142835
_coding style issues_
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#244: FILE: drivers/bus/dpaa/base/fman/fman.c:868:
+ FMAN_ERR(-EINVAL, "%s: couldn't get p_onic_oh_nodes
",
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#251: FILE: drivers/bus/dpaa/base/fman/fman.c:875:
+ FMAN_ERR(-EINVAL, "%s: couldn't get rx_oh_node
",
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#259: FILE: drivers/bus/dpaa/base/fman/fman.c:883:
+ FMAN_ERR(-EINVAL, "%s: couldn't get p_fman_rx_oh_node
",
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#266: FILE: drivers/bus/dpaa/base/fman/fman.c:890:
+ FMAN_ERR(-EINVAL, "%s: couldn't get fman_rx_oh_node
",
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#298: FILE: drivers/bus/dpaa/base/fman/fman.c:922:
+ FMAN_ERR(-EINVAL, "%s: couldn't get tx_oh_node
",
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#306: FILE: drivers/bus/dpaa/base/fman/fman.c:930:
+ FMAN_ERR(-EINVAL, "%s: couldn't get p_fman_tx_oh_node
",
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#313: FILE: drivers/bus/dpaa/base/fman/fman.c:937:
+ FMAN_ERR(-EINVAL, "%s: couldn't get fman_tx_oh_node
",
total: 0 errors, 7 warnings, 0 checks, 799 lines checked
parent reply other threads:[~2024-08-01 10:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240801105313.630280-16-hemant.agrawal@nxp.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=20240801105550.D9BFD123EF2@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=hemant.agrawal@nxp.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).