From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Chaoyong He <chaoyong.he@corigine.com>
Subject: |WARNING| pw127084 [PATCH] doc: announce inclusive naming function name changes
Date: Fri, 19 May 2023 08:37:11 +0200 (CEST) [thread overview]
Message-ID: <20230519063711.3847C120927@dpdk.org> (raw)
In-Reply-To: <20230519063334.1645933-1-chaoyong.he@corigine.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/127084
_coding style issues_
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#116: FILE: doc/guides/rel_notes/deprecation.rst:167:
+* bonding: References to slave will be removed in DPDK 23.11. The following
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#119: FILE: doc/guides/rel_notes/deprecation.rst:170:
+ ``rte_eth_bond_8023ad_slave_info``,
WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#120: FILE: doc/guides/rel_notes/deprecation.rst:171:
+ ``rte_eth_bond_active_slaves_get``,
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#121: FILE: doc/guides/rel_notes/deprecation.rst:172:
+ ``rte_eth_bond_slave_add``, ``rte_eth_bond_slave_remove``, and
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#121: FILE: doc/guides/rel_notes/deprecation.rst:172:
+ ``rte_eth_bond_slave_add``, ``rte_eth_bond_slave_remove``, and
WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#122: FILE: doc/guides/rel_notes/deprecation.rst:173:
+ ``rte_eth_bond_slaves_get`` will be replaced by:
total: 0 errors, 6 warnings, 15 lines checked
next prev parent reply other threads:[~2023-05-19 6:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230519063334.1645933-1-chaoyong.he@corigine.com>
2023-05-19 6:25 ` |SUCCESS| " qemudev
2023-05-19 6:29 ` qemudev
2023-05-19 6:37 ` checkpatch [this message]
2023-05-19 7:39 ` 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=20230519063711.3847C120927@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=chaoyong.he@corigine.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).