From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ke Zhang <ke1x.zhang@intel.com>
Subject: |WARNING| pw109416 [PATCH] net/bonding: fix rss key configuration when the key length is 52
Date: Thu, 7 Apr 2022 11:42:54 +0200 (CEST) [thread overview]
Message-ID: <20220407094254.16F10124163@dpdk.org> (raw)
In-Reply-To: <20220407093642.44900-1-ke1x.zhang@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/109416
_coding style issues_
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#64:
when creating a bonding device, if the slave device's rss key length
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#65:
is 52, then bonding device will be same as slave, in function
total: 0 errors, 2 warnings, 0 checks, 19 lines checked
next parent reply other threads:[~2022-04-07 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220407093642.44900-1-ke1x.zhang@intel.com>
2022-04-07 9:42 ` checkpatch [this message]
2022-04-07 11:59 ` |SUCCESS| " 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=20220407094254.16F10124163@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ke1x.zhang@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).