From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: [dpdk-test-report] |WARNING| pw89257 [PATCH 2/2] qos: rearrange enqueue procedure
Date: Tue, 16 Mar 2021 18:08:23 +0100 (CET) [thread overview]
Message-ID: <20210316170823.8A69F2BE3@dpdk.org> (raw)
In-Reply-To: <20210316170723.22036-2-konstantin.ananyev@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/89257
_coding style issues_
WARNING:TYPO_SPELLING: 'futher' may be misspelled - perhaps 'further'?
#60:
That helps to avoid load stalls at futher stages of enqueue()
WARNING:TYPO_SPELLING: 'perfomance' may be misspelled - perhaps 'performance'?
#61:
and improves overall enqueue perfomance.
total: 0 errors, 2 warnings, 272 lines checked
next parent reply other threads:[~2021-03-16 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210316170723.22036-2-konstantin.ananyev@intel.com>
2021-03-16 17:08 ` checkpatch [this message]
2021-03-16 19:05 ` [dpdk-test-report] |FAILURE| pw89257 " 0-day Robot
2021-03-16 19:06 ` [dpdk-test-report] |FAILURE| pw89257 [dpdk-dev] [PATCH 2/2] " 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=20210316170823.8A69F2BE3@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=konstantin.ananyev@intel.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).