From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Yipeng Wang <yipeng1.wang@intel.com>,
Sameh Gobriel <sameh.gobriel@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
Wathsala Vithanage <wathsala.vithanage@arm.com>,
Vamsi Attunuru <vattunuru@marvell.com>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Subject: [PATCH] replace use of word segregate in comments
Date: Fri, 4 Oct 2024 16:03:04 -0700 [thread overview]
Message-ID: <20241004230305.72516-1-stephen@networkplumber.org> (raw)
The use of the word segregate should be avoided.
Rationale from https://inclusivenaming.org/word-lists/tier-3/segregate/
The word segregation carries strong context in regard to civil rights
movements in the US and South Africa, segregation in the US South, and
racist history.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
app/test/test_hash_readwrite_lf_perf.c | 2 +-
drivers/net/octeon_ep/cnxk_ep_rx_neon.c | 2 +-
drivers/net/octeon_ep/cnxk_ep_rx_sse.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/app/test/test_hash_readwrite_lf_perf.c b/app/test/test_hash_readwrite_lf_perf.c
index 4523985169..864c3059d9 100644
--- a/app/test/test_hash_readwrite_lf_perf.c
+++ b/app/test/test_hash_readwrite_lf_perf.c
@@ -397,7 +397,7 @@ generate_keys(void)
for (i = 2; i < TOTAL_INSERT; i++)
keys[i] = keys[i-1] + keys[i-2];
- /* Segregate keys into keys_no_ks and keys_ks */
+ /* Separate keys into keys_no_ks and keys_ks */
for (i = 0; i < TOTAL_INSERT; i++) {
/* Check if primary bucket has space.*/
sig = rte_hash_hash(tbl_rwc_test_param.h,
diff --git a/drivers/net/octeon_ep/cnxk_ep_rx_neon.c b/drivers/net/octeon_ep/cnxk_ep_rx_neon.c
index 4c46a7ea08..2e17f2dfec 100644
--- a/drivers/net/octeon_ep/cnxk_ep_rx_neon.c
+++ b/drivers/net/octeon_ep/cnxk_ep_rx_neon.c
@@ -61,7 +61,7 @@ cnxk_ep_process_pkts_vec_neon(struct rte_mbuf **rx_pkts, struct otx_ep_droq *dro
/* Vertical add, consolidate outside the loop. */
bytes += vaddq_u32(bytes, s01);
- /* Segregate to packet length and data length. */
+ /* Separate intto packet length and data length. */
s23 = vqtbl1q_u8(s01, mask1);
s01 = vqtbl1q_u8(s01, mask0);
diff --git a/drivers/net/octeon_ep/cnxk_ep_rx_sse.c b/drivers/net/octeon_ep/cnxk_ep_rx_sse.c
index 308c8b2288..cab26ddaf3 100644
--- a/drivers/net/octeon_ep/cnxk_ep_rx_sse.c
+++ b/drivers/net/octeon_ep/cnxk_ep_rx_sse.c
@@ -52,7 +52,7 @@ cnxk_ep_process_pkts_vec_sse(struct rte_mbuf **rx_pkts, struct otx_ep_droq *droq
s01 = _mm_shuffle_epi8(s01, bswap_mask);
/* Vertical add, consolidate outside loop */
bytes = _mm_add_epi32(bytes, s01);
- /* Segregate to packet length and data length. */
+ /* Separate intto packet length and data length. */
s23 = _mm_shuffle_epi32(s01, _MM_SHUFFLE(3, 3, 1, 1));
s01 = _mm_shuffle_epi8(s01, cpy_mask);
s23 = _mm_shuffle_epi8(s23, cpy_mask);
--
2.45.2
reply other threads:[~2024-10-04 23:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20241004230305.72516-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=sameh.gobriel@intel.com \
--cc=vattunuru@marvell.com \
--cc=vladimir.medvedkin@intel.com \
--cc=wathsala.vithanage@arm.com \
--cc=yipeng1.wang@intel.com \
/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).