From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Joyce Kong <joyce.kong@arm.com>
Subject: [dpdk-test-report] |WARNING| pw86663 [PATCH v1] eal/arm: fix gcc build for 128-bit atomic compare exchange
Date: Fri, 15 Jan 2021 10:59:21 +0100 (CET) [thread overview]
Message-ID: <20210115095921.7C22B2901@dpdk.org> (raw)
In-Reply-To: <20210115095821.42721-1-joyce.kong@arm.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/86663
_coding style issues_
WARNING:TYPO_SPELLING: 'cas' may be misspelled - perhaps 'case'?
#56:
function ‘__cas_128_relaxed’:
WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#59:
__ATOMIC128_CAS_OP(__cas_128_relaxed, "casp")
WARNING:TYPO_SPELLING: 'cas' may be misspelled - perhaps 'case'?
#59:
__ATOMIC128_CAS_OP(__cas_128_relaxed, "casp")
WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'?
#62:
Fix the compiling issue by defining __ATOMIC128_CAS_OP as a void
WARNING:TYPO_SPELLING: 'cas' may be misspelled - perhaps 'case'?
#84: FILE: lib/librte_eal/arm/include/rte_atomic_64.h:57:
+cas_op_name(rte_int128_t *dst, rte_int128_t *old, rte_int128_t updated) \
WARNING:TYPO_SPELLING: 'cas' may be misspelled - perhaps 'case'?
#114: FILE: lib/librte_eal/arm/include/rte_atomic_64.h:115:
+ __cas_128_relaxed(dst, exp, desired);
WARNING:TYPO_SPELLING: 'cas' may be misspelled - perhaps 'case'?
#117: FILE: lib/librte_eal/arm/include/rte_atomic_64.h:117:
+ __cas_128_acquire(dst, exp, desired);
WARNING:TYPO_SPELLING: 'cas' may be misspelled - perhaps 'case'?
#120: FILE: lib/librte_eal/arm/include/rte_atomic_64.h:119:
+ __cas_128_release(dst, exp, desired);
WARNING:TYPO_SPELLING: 'cas' may be misspelled - perhaps 'case'?
#123: FILE: lib/librte_eal/arm/include/rte_atomic_64.h:121:
+ __cas_128_acq_rel(dst, exp, desired);
total: 0 errors, 9 warnings, 63 lines checked
next parent reply other threads:[~2021-01-15 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210115095821.42721-1-joyce.kong@arm.com>
2021-01-15 9:59 ` checkpatch [this message]
2021-01-20 3:03 [dpdk-test-report] |WARNING| pw86663 [PATCH] [v1] " dpdklab
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=20210115095921.7C22B2901@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=joyce.kong@arm.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).