automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw139019 [PATCH 2/4] doc: replace ifconfig and brctl usage in howto
Date: Tue,  2 Apr 2024 18:31:36 +0200 (CEST)	[thread overview]
Message-ID: <20240402163136.B3B5C1223FE@dpdk.org> (raw)
In-Reply-To: <20240402163050.133923-3-stephen@networkplumber.org>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/139019

_coding style issues_


WARNING:TYPO_SPELLING: 'lastest' may be misspelled - perhaps 'latest'?
#84: 
The brctl command is deprecated and not supported on lastest

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#123: FILE: doc/guides/howto/lm_bond_virtio_sriov.rst:454:
+   ip link set dev ens3f0 master virbr0

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#124: FILE: doc/guides/howto/lm_bond_virtio_sriov.rst:455:
+   ip link set dev ens6f0 master virbr0

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#125: FILE: doc/guides/howto/lm_bond_virtio_sriov.rst:456:
+   ip link set dev tap1 master virbr0

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#154: FILE: doc/guides/howto/lm_bond_virtio_sriov.rst:557:
+   ip link set dev ens4f0 master virbr0

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#155: FILE: doc/guides/howto/lm_bond_virtio_sriov.rst:558:
+   ip link set dev ens5f0 master virbr0

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#156: FILE: doc/guides/howto/lm_bond_virtio_sriov.rst:559:
+   ip link set dev tap1 master virbr0

total: 0 errors, 7 warnings, 86 lines checked

           reply	other threads:[~2024-04-02 16:31 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20240402163050.133923-3-stephen@networkplumber.org>]

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=20240402163136.B3B5C1223FE@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=stephen@networkplumber.org \
    --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).