From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Gregory Etelson <getelson@nvidia.com>
Subject: [dpdk-test-report] |WARNING| pw91282 [PATCH v3 1/2] ethdev: add packet integrity checks
Date: Tue, 13 Apr 2021 17:16:53 +0200 (CEST) [thread overview]
Message-ID: <20210413151653.BF0271209EC@dpdk.org> (raw)
In-Reply-To: <20210413151606.11522-2-getelson@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/91282
_coding style issues_
WARNING:TYPO_SPELLING: 'currenlty' may be misspelled - perhaps 'currently'?
#138:
Since currenlty rte_flow works in positive way the assumtion is
WARNING:TYPO_SPELLING: 'assumtion' may be misspelled - perhaps 'assumption'?
#138:
Since currenlty rte_flow works in positive way the assumtion is
WARNING:TYPO_SPELLING: 'postive' may be misspelled - perhaps 'positive'?
#139:
that the postive way will be the common way in this case also.
WARNING:TYPO_SPELLING: 'Flexability' may be misspelled - perhaps 'Flexibility'?
#148:
6. Flexability.
WARNING:TYPO_SPELLING: 'doens' may be misspelled - perhaps 'does'?
#184:
3. l3_ok - all check for layer 3 have passed. If packet doens't have
total: 0 errors, 5 warnings, 84 lines checked
parent reply other threads:[~2021-04-13 15:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210413151606.11522-2-getelson@nvidia.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=20210413151653.BF0271209EC@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=getelson@nvidia.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).