From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw100402 [PATCH v3 1/2] hash: split x86 and SW hash CRC intrinsics
Date: Mon, 4 Oct 2021 01:02:09 +0200 (CEST) [thread overview]
Message-ID: <20211003230209.A8259120DFE@dpdk.org> (raw)
In-Reply-To: <20211003230008.12730-1-pbhagavatula@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/100402
_coding style issues_
WARNING:TYPO_SPELLING: 'EDE' may be misspelled - perhaps 'EDGE'?
#127: FILE: lib/hash/hash_crc_sw.h:15:
+ 0xBC267848, 0x4E4DFB4B, 0x20BD8EDE, 0xD2D60DDD, 0xC186FE29, 0x33ED7D2A,
WARNING:TYPO_SPELLING: 'AFE' may be misspelled - perhaps 'SAFE'?
#193: FILE: lib/hash/hash_crc_sw.h:81:
+ 0x195CDA43, 0x0AFE4234, 0x3E19EAAD, 0x2DBB72DA, 0x57D6BB9F, 0x447423E8,
WARNING:TYPO_SPELLING: 'AFE' may be misspelled - perhaps 'SAFE'?
#290: FILE: lib/hash/hash_crc_sw.h:178:
+ 0x6700C234, 0xBA45688C, 0xA345D046, 0x7E007AFE, 0x1C22F3C7, 0xC167597F,
WARNING:TYPO_SPELLING: 'DED' may be misspelled - perhaps 'DEAD'?
#300: FILE: lib/hash/hash_crc_sw.h:188:
+ 0xFBED0BE7, 0xC3FC644B, 0x8BCFD4BF, 0xB3DEBB13, 0xDECFBEC6, 0xE6DED16A,
WARNING:TYPO_SPELLING: 'EDE' may be misspelled - perhaps 'EDGE'?
#313: FILE: lib/hash/hash_crc_sw.h:201:
+ 0xD3F96172, 0xEBE80EDE, 0x439E009A, 0x7B8F6F36, 0x33BCDFC2, 0x0BADB06E,
WARNING:TYPO_SPELLING: 'EDE' may be misspelled - perhaps 'EDGE'?
#333: FILE: lib/hash/hash_crc_sw.h:221:
+ 0xF71EDE6C, 0xCF0FB1C0, 0x6779BF84, 0x5F68D028, 0x175B60DC, 0x2F4A0F70,
WARNING:TYPO_SPELLING: 'DAA' may be misspelled - perhaps 'DATA'?
#345: FILE: lib/hash/hash_crc_sw.h:233:
+ 0x45F826B3, 0xAAC84DAA, 0x9E748670, 0x7144ED69, 0xF70D11C4, 0x183D7ADD,
total: 0 errors, 7 warnings, 889 lines checked
parent reply other threads:[~2021-10-03 23:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20211003230008.12730-1-pbhagavatula@marvell.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=20211003230209.A8259120DFE@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=pbhagavatula@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).