From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Sarosh Arif <sarosh.arif@emumba.com>
Subject: [dpdk-test-report] |WARNING| pw87848 [v2 PATCH] doc: replace testpmd with dpdk-testpmd in all commands
Date: Tue, 16 Feb 2021 10:36:10 +0100 (CET) [thread overview]
Message-ID: <20210216093610.17DFFC906@dpdk.org> (raw)
In-Reply-To: <20210211071937.21906-1-sarosh.arif@emumba.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/87848
_coding style issues_
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#130: FILE: doc/guides/nics/bnxt.rst:850:
+ dpdk-testpmd -l 0-3 -n4 --vdev 'net_bonding0,mode=0,slave=<PCI B:D.F device 1>,slave=<PCI B:D.F device 2>,mac=XX:XX:XX:XX:XX:XX’ – --socket_num=1 – -i --port-topology=chained
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#130: FILE: doc/guides/nics/bnxt.rst:850:
+ dpdk-testpmd -l 0-3 -n4 --vdev 'net_bonding0,mode=0,slave=<PCI B:D.F device 1>,slave=<PCI B:D.F device 2>,mac=XX:XX:XX:XX:XX:XX’ – --socket_num=1 – -i --port-topology=chained
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#131: FILE: doc/guides/nics/bnxt.rst:851:
+ (ex) dpdk-testpmd -l 1,3,5,7,9 -n4 --vdev 'net_bonding0,mode=0,slave=0000:82:00.0,slave=0000:82:00.1,mac=00:1e:67:1d:fd:1d' – --socket-num=1 – -i --port-topology=chained
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#131: FILE: doc/guides/nics/bnxt.rst:851:
+ (ex) dpdk-testpmd -l 1,3,5,7,9 -n4 --vdev 'net_bonding0,mode=0,slave=0000:82:00.0,slave=0000:82:00.1,mac=00:1e:67:1d:fd:1d' – --socket-num=1 – -i --port-topology=chained
total: 0 errors, 4 warnings, 90 lines checked
parent reply other threads:[~2021-02-16 9:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210211071937.21906-1-sarosh.arif@emumba.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=20210216093610.17DFFC906@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=sarosh.arif@emumba.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).