DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Coleman <omegacoleman@gmail.com>
To: dev@dpdk.org
Cc: Ray Kinsella <mdr@ashroe.eu>
Subject: [PATCH] doc: fix typos 'depreciated' instead of 'deprecated'
Date: Tue, 19 Apr 2022 17:01:02 +0800	[thread overview]
Message-ID: <CAPTjMhhkHwOwAPGwVpjptnLdCcYmWqNA15p5ZUKa6FPiWPq9VQ@mail.gmail.com> (raw)

From 1871ee6f7b98ef89b7c4893d90b5ea264660c201 Mon Sep 17 00:00:00 2001
From: youcai <omegacoleman@gmail.com>
Date: Tue, 19 Apr 2022 14:38:36 +0800
Subject: [PATCH] doc: fix typos 'depreciated' instead of 'deprecated'
Cc: Ray Kinsella <mdr@ashroe.eu>

Same issue was fixed in ABI policy in ec5c0f8, but more of this
misuse persist in comments and docs. 'depreciated' means diminish
in value over a period of time. It should not appear here.

Signed-off-by: youcai <omegacoleman@gmail.com>
---
 doc/guides/contributing/abi_policy.rst     | 2 +-
 doc/guides/contributing/abi_versioning.rst | 2 +-
 lib/kni/rte_kni.h                          | 4 ++--
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/guides/contributing/abi_policy.rst
b/doc/guides/contributing/abi_policy.rst
index 64919b6a2b..5fd4052585 100644
--- a/doc/guides/contributing/abi_policy.rst
+++ b/doc/guides/contributing/abi_policy.rst
@@ -167,7 +167,7 @@ The requirements for changing the ABI are:
    API becomes non-experimental, then the old one is marked with
    ``__rte_deprecated``.

-    - The depreciated API should follow the notification process to be removed,
+    - The deprecated API should follow the notification process to be removed,
       see  :ref:`deprecation_notices`.

     - At the declaration of the next major ABI version, those ABI changes then
diff --git a/doc/guides/contributing/abi_versioning.rst
b/doc/guides/contributing/abi_versioning.rst
index dd96527ee5..7afd1c1886 100644
--- a/doc/guides/contributing/abi_versioning.rst
+++ b/doc/guides/contributing/abi_versioning.rst
@@ -94,7 +94,7 @@ that library.
  ...

 However when a new ABI version is declared, for example DPDK ``22``, old
-depreciated functions may be safely removed at this point and the entire old
+deprecated functions may be safely removed at this point and the entire old
 major ABI version removed, see the section :ref:`deprecating_entire_abi` on
 how this may be done.

diff --git a/lib/kni/rte_kni.h b/lib/kni/rte_kni.h
index b85d3dd32b..f6ef572a82 100644
--- a/lib/kni/rte_kni.h
+++ b/lib/kni/rte_kni.h
@@ -64,8 +64,8 @@ struct rte_kni_conf {
     uint32_t core_id;   /* Core ID to bind kernel thread on */
     uint16_t group_id;  /* Group ID */
     unsigned mbuf_size; /* mbuf size */
-    struct rte_pci_addr addr; /* depreciated */
-    struct rte_pci_id id; /* depreciated */
+    struct rte_pci_addr addr; /* deprecated */
+    struct rte_pci_id id; /* deprecated */

     __extension__
     uint8_t force_bind : 1; /* Flag to bind kernel thread */
-- 
2.17.1

             reply	other threads:[~2022-04-19  9:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19  9:01 Stephen Coleman [this message]
2022-04-19 15:44 ` Ray Kinsella
2022-11-15 16:13   ` Thomas Monjalon

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=CAPTjMhhkHwOwAPGwVpjptnLdCcYmWqNA15p5ZUKa6FPiWPq9VQ@mail.gmail.com \
    --to=omegacoleman@gmail.com \
    --cc=dev@dpdk.org \
    --cc=mdr@ashroe.eu \
    /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).