From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>, <dev@dpdk.org>
Cc: "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: RE: [PATCH] replace use of word segregate in comments
Date: Tue, 8 Oct 2024 11:53:24 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F795@smartserver.smartshare.dk> (raw)
In-Reply-To: <20241004230305.72516-1-stephen@networkplumber.org>
> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> Sent: Saturday, 5 October 2024 01.03
>
> 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>
> ---
> +++ 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. */
Typo: intto -> into
> +++ 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. */
Typo: intto -> into
With typos fixed,
Acked-by: Morten Brørup <mb@smartsharesystems.com>
next prev parent reply other threads:[~2024-10-08 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 23:03 Stephen Hemminger
2024-10-08 9:53 ` Morten Brørup [this message]
2024-10-08 15:49 ` [PATCH v2] " Stephen Hemminger
2024-10-09 0:36 ` fengchengwen
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=98CBD80474FA8B44BF855DF32C47DC35E9F795@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=sameh.gobriel@intel.com \
--cc=stephen@networkplumber.org \
--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).