From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ori Kam <orika@nvidia.com>
Subject: [dpdk-test-report] |WARNING| pw90567 [PATCH] ethdev: add packet integrity checks
Date: Mon, 5 Apr 2021 20:06:05 +0200 (CEST) [thread overview]
Message-ID: <20210405180605.8CB51120D42@dpdk.org> (raw)
In-Reply-To: <1617645874-105139-1-git-send-email-orika@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/90567
_coding style issues_
WARNING:TYPO_SPELLING: 'currenlty' may be misspelled - perhaps 'currently'?
#62:
Since currenlty rte_flow works in positive way the assumtion is
WARNING:TYPO_SPELLING: 'assumtion' may be misspelled - perhaps 'assumption'?
#62:
Since currenlty rte_flow works in positive way the assumtion is
WARNING:TYPO_SPELLING: 'postive' may be misspelled - perhaps 'positive'?
#63:
that the postive way will be the common way in this case also.
WARNING:TYPO_SPELLING: 'Flexability' may be misspelled - perhaps 'Flexibility'?
#72:
6. Flexability.
WARNING:TYPO_SPELLING: 'doens' may be misspelled - perhaps 'does'?
#108:
3. l3_ok - all check flor layer 2 have passed. If packet doens't have
WARNING:TYPO_SPELLING: 'shoudl' may be misspelled - perhaps 'should'?
#109:
l3 layer this check shoudl fail.
total: 0 errors, 6 warnings, 83 lines checked
next parent reply other threads:[~2021-04-05 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1617645874-105139-1-git-send-email-orika@nvidia.com>
2021-04-05 18:06 ` checkpatch [this message]
2021-04-05 19:55 ` [dpdk-test-report] |FAILURE| pw90567 " 0-day Robot
2021-04-05 20:57 ` [dpdk-test-report] |FAILURE| pw90567 [dpdk-dev] [PATCH] " 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=20210405180605.8CB51120D42@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=orika@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).