From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw136339 [PATCH] drivers: Convert uses of RTE_LOG_DP to use RTE_LOG_DP_LINE
Date: Fri, 2 Feb 2024 18:40:51 +0100 (CET) [thread overview]
Message-ID: <20240202174051.6F852121F08@dpdk.org> (raw)
In-Reply-To: <20240202174006.63373-1-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/136339
_coding style issues_
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#283: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1151:
+ DPAA2_SEC_DP_DEBUG("CIPHER SG: 1 - flc = %p, fle = %p FLEaddr = %x-%x, len %d",
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#284: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1152:
+ flc, fle, fle->addr_hi, fle->addr_lo, fle->length);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#284: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1152:
+ flc, fle, fle->addr_hi, fle->addr_lo, fle->length);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#284: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1152:
+ flc, fle, fle->addr_hi, fle->addr_lo, fle->length);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#284: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1152:
+ flc, fle, fle->addr_hi, fle->addr_lo, fle->length);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#329: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1271:
+ DPAA2_SEC_DP_DEBUG("CIPHER: 1 - flc = %p, fle = %p FLEaddr = %x-%x, length %d",
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#330: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1272:
+ flc, fle, fle->addr_hi, fle->addr_lo, fle->length);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#330: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1272:
+ flc, fle, fle->addr_hi, fle->addr_lo, fle->length);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#330: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1272:
+ flc, fle, fle->addr_hi, fle->addr_lo, fle->length);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#330: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1272:
+ flc, fle, fle->addr_hi, fle->addr_lo, fle->length);
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#391: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1532:
+ DPAA2_SEC_DP_DEBUG("FLE addr = %x - %x, offset = %x",
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#488: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:641:
+ DPAA2_SEC_DP_DEBUG("RAW CIPHER SG: 1 - flc = %p, fle = %p FLEaddr = %x-%x, len %d",
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#489: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:642:
+ flc, fle, fle->addr_hi, fle->addr_lo, fle->length);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#489: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:642:
+ flc, fle, fle->addr_hi, fle->addr_lo, fle->length);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#489: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:642:
+ flc, fle, fle->addr_hi, fle->addr_lo, fle->length);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#489: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:642:
+ flc, fle, fle->addr_hi, fle->addr_lo, fle->length);
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#513: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_raw_dp.c:807:
+ DPAA2_SEC_DP_DEBUG("FLE addr = %x - %x, offset = %x",
total: 0 errors, 17 warnings, 1010 lines checked
next prev parent reply other threads:[~2024-02-02 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240202174006.63373-1-stephen@networkplumber.org>
2024-02-02 17:17 ` |SUCCESS| " qemudev
2024-02-02 17:21 ` qemudev
2024-02-02 17:40 ` checkpatch [this message]
2024-02-02 18:44 ` 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=20240202174051.6F852121F08@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=stephen@networkplumber.org \
--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).