From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: David Miller <dmiller423@gmail.com>
Subject: |WARNING| pw129704 [PATCH v3] Add support for IBM Z s390x
Date: Wed, 26 Jul 2023 03:36:18 +0200 (CEST) [thread overview]
Message-ID: <20230726013618.8B9E612092E@dpdk.org> (raw)
In-Reply-To: <20230726013517.216549-1-dmiller423@gmail.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/129704
_coding style issues_
WARNING:TYPO_SPELLING: 'daa' may be misspelled - perhaps 'data'?
#477: FILE: app/test/test_hash_functions.c:77:
+ 0x37765e57, 0x6559eb17, 0x49c8a164, 0x18daa0d3,
WARNING:TYPO_SPELLING: 'avaialbe' may be misspelled - perhaps 'available'?
#1129: FILE: drivers/net/i40e/i40e_rxtx_vec_s390x.c:448:
+ /* C.4 calc avaialbe number of desc */
WARNING:TYPO_SPELLING: 'signifcant' may be misspelled - perhaps 'significant'?
#1879: FILE: lib/acl/acl_gen.c:365:
+ * is at least signifcant byte.
total: 0 errors, 3 warnings, 2744 lines checked
Warning in drivers/net/i40e/i40e_rxtx_vec_s390x.c:
Using compiler attribute directly
Warning in lib/eal/s390x/include/rte_atomic.h:
Using rte_smp_[r/w]mb
Warning in lib/eal/s390x/include/rte_spinlock.h:
Using __sync_xxx builtins
next prev parent reply other threads:[~2023-07-26 1:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230726013517.216549-1-dmiller423@gmail.com>
2023-07-26 1:31 ` |SUCCESS| " qemudev
2023-07-26 1:35 ` qemudev
2023-07-26 1:36 ` checkpatch [this message]
2023-07-26 2:18 ` |FAILURE| " 0-day Robot
2023-07-26 2:13 |WARNING| pw129704 [PATCH] [v3] " dpdklab
2023-07-26 2:13 dpdklab
2023-07-26 2:14 dpdklab
2023-07-26 2:15 dpdklab
2023-07-26 2:26 dpdklab
2023-07-26 2:30 dpdklab
2023-07-26 2:30 dpdklab
2023-07-26 2:32 dpdklab
2023-07-26 2:34 dpdklab
2023-07-26 2:35 dpdklab
2023-07-26 2:35 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=20230726013618.8B9E612092E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=dmiller423@gmail.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).