All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ashwin Sekhar T K <asekhar@marvell.com>
To: <dev@dpdk.org>
Cc: <jerinj@marvell.com>, <skori@marvell.com>,
	<skoteshwar@marvell.com>, <pbhagavatula@marvell.com>,
	<kirankumark@marvell.com>, <psatheesh@marvell.com>,
	<asekhar@marvell.com>, <anoobj@marvell.com>, <gakhil@marvell.com>,
	<ferruh.yigit@intel.com>, <david.marchand@redhat.com>,
	<thomas@monjalon.net>
Subject: [dpdk-dev] [PATCH v3] devtools: add acronyms in dictionary for commit checks
Date: Fri, 17 Sep 2021 16:28:39 +0530	[thread overview]
Message-ID: <20210917105839.270289-1-asekhar@marvell.com> (raw)
In-Reply-To: <20210917100330.269797-1-asekhar@marvell.com>

Update word list with Marvell specific acronyms.

CPT  -> Cryptographic Accelerator Unit
CQ   -> Completion Queue
LBK  -> Loopback Interface Unit
LMT  -> Large Atomic Store Unit
MCAM -> Match Content Addressable Memory
NIX  -> Network Interface Controller Unit
NPA  -> Network Pool Allocator
NPC  -> Network Parser and CAM Unit
ROC  -> Rest Of Chip
RQ   -> Receive Queue
RVU  -> Resource Virtualization Unit
SQ   -> Send Queue
SSO  -> Schedule Synchronize Order Unit
TIM  -> Timer Unit

Signed-off-by: Ashwin Sekhar T K <asekhar@marvell.com>
---
 devtools/words-case.txt | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/devtools/words-case.txt b/devtools/words-case.txt
index 0bbad48626..0ea23689f0 100644
--- a/devtools/words-case.txt
+++ b/devtools/words-case.txt
@@ -6,6 +6,8 @@ Arm
 armv7
 armv8
 BAR
+CPT
+CQ
 CRC
 DCB
 DevX
@@ -33,10 +35,13 @@ L2
 L3
 L4
 LACP
+LBK
 Linux
+LMT
 LRO
 LSC
 MAC
+MCAM
 MPLS
 MSI
 MSI-X
@@ -44,6 +49,9 @@ MSS
 MTU
 NEON
 NIC
+NIX
+NPA
+NPC
 null
 NUMA
 NVGRE
@@ -57,15 +65,21 @@ PVID
 QinQ
 RDMA
 RETA
+ROC
+RQ
 RSS
+RVU
 Rx
 SCTP
 SMP
 SoC
+SQ
+SSO
 SW
 TC
 TCAM
 Thor
+TIM
 TOS
 TPID
 TSO
-- 
2.32.0


  parent reply	other threads:[~2021-09-17 11:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17 10:03 [dpdk-dev] [PATCH v1] devtools: add acronyms in dictionary for commit checks Ashwin Sekhar T K
2021-09-17 10:06 ` [dpdk-dev] [PATCH v2] " Ashwin Sekhar T K
2021-09-17 10:58 ` Ashwin Sekhar T K [this message]
2021-09-17 11:03   ` [dpdk-dev] [PATCH v3] " Jerin Jacob
2021-11-25 11:30     ` Thomas Monjalon
2021-09-17 12:55   ` Thomas Monjalon
2021-09-17 13:54     ` [dpdk-dev] [EXT] " Ashwin Sekhar Thalakalath Kottilveetil
2021-09-17 14:05       ` Thomas Monjalon
2021-09-17 14:53         ` Ashwin Sekhar Thalakalath Kottilveetil
2021-09-17 16:15           ` Thomas Monjalon
2021-09-20  9:05             ` Ferruh Yigit
2021-09-20  9:19               ` Ashwin Sekhar Thalakalath Kottilveetil
2021-09-20 10:31                 ` Ferruh Yigit
2021-09-20  9:07   ` [dpdk-dev] " Ferruh Yigit
2021-09-20  9:10     ` Jerin Jacob
2021-09-20 10:32       ` Ferruh Yigit
2021-11-03 16:44         ` Ferruh Yigit
2021-09-20  9:21     ` [dpdk-dev] [EXT] " Ashwin Sekhar Thalakalath Kottilveetil

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=20210917105839.270289-1-asekhar@marvell.com \
    --to=asekhar@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=gakhil@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=kirankumark@marvell.com \
    --cc=pbhagavatula@marvell.com \
    --cc=psatheesh@marvell.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@marvell.com \
    --cc=thomas@monjalon.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.