From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Bing Zhao <bingz@nvidia.com>
Subject: [dpdk-test-report] |WARNING| pw90884 [RFC PATCH v2] ethdev: introduce indirect action APIs
Date: Thu, 8 Apr 2021 16:46:53 +0200 (CEST) [thread overview]
Message-ID: <20210408144653.A9EEC120D42@dpdk.org> (raw)
In-Reply-To: <1617893160-93131-1-git-send-email-bingz@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/90884
_coding style issues_
WARNING:TYPO_SPELLING: 'shoule' may be misspelled - perhaps 'should'?
#49:
actions, like RSS, count. The shared action shoule be created before
WARNING:TYPO_SPELLING: 'paramter' may be misspelled - perhaps 'parameter'?
#90:
action, such pointer paramter may not meet the need.
WARNING:TYPO_SPELLING: 'orginal' may be misspelled - perhaps 'original'?
#314: FILE: lib/librte_ethdev/rte_flow.h:3773:
+ * Query the orginal action by corresponding indirect action object handle.
total: 0 errors, 3 warnings, 259 lines checked
parent reply other threads:[~2021-04-08 14:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1617893160-93131-1-git-send-email-bingz@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=20210408144653.A9EEC120D42@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=bingz@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).