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: [dpdk-test-report] |WARNING| pw75257 [PATCH v3 20.08 1/6] doc: announce deprecation of master lcore
Date: Thu,  6 Aug 2020 19:20:35 +0200 (CEST)	[thread overview]
Message-ID: <20200806172035.C20891C0D4@dpdk.org> (raw)
In-Reply-To: <20200806171947.6609-2-stephen@networkplumber.org>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#65: 
Subject: [dpdk-dev] [PATCH v3 20.08 1/6] doc: announce deprecation of master

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#81: 
Announce upcoming changes related to master/slave in reference

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#81: 
Announce upcoming changes related to master/slave in reference

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#100: FILE: doc/guides/rel_notes/deprecation.rst:257:
+  will replace uses of master/slave in the API's and command line arguments.

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#100: FILE: doc/guides/rel_notes/deprecation.rst:257:
+  will replace uses of master/slave in the API's and command line arguments.

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#102: FILE: doc/guides/rel_notes/deprecation.rst:259:
+  References to master/slave in relation to lcore will be renamed

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#102: FILE: doc/guides/rel_notes/deprecation.rst:259:
+  References to master/slave in relation to lcore will be renamed

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#103: FILE: doc/guides/rel_notes/deprecation.rst:260:
+  to initial/worker.  The function ``rte_get_master_lcore()``

WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#110: FILE: doc/guides/rel_notes/deprecation.rst:267:
+  ``RTE_LCORE_FOREACH_SLAVE`` will be replaced with

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#113: FILE: doc/guides/rel_notes/deprecation.rst:270:
+  The ``master-lcore`` argument to testpmd will be replaced

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#114: FILE: doc/guides/rel_notes/deprecation.rst:271:
+  with ``initial-lcore``. The old ``master-lcore`` argument

total: 0 errors, 11 warnings, 23 lines checked

           reply	other threads:[~2020-08-06 17:20 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20200806171947.6609-2-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=20200806172035.C20891C0D4@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).