From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, "Morten Brørup" <mb@smartsharesystems.com>,
"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>,
fengchengwen <fengchengwen@huawei.com>
Subject: Re: [PATCH v2] replace use of word segregate in comments
Date: Tue, 26 Nov 2024 23:58:52 +0100 [thread overview]
Message-ID: <4856624.jE0xQCEvom@thomas> (raw)
In-Reply-To: <1c3ae90a-a050-4238-af4c-587c9a33ba85@huawei.com>
09/10/2024 02:36, fengchengwen:
> Acked-by: Chengwen Feng <fengchengwen@huawei.com>
>
> On 2024/10/8 23:49, Stephen Hemminger wrote:
> > 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>
> > Acked-by: Morten Brørup <mb@smartsharesystems.com>
Applied, thanks.
prev parent reply other threads:[~2024-11-26 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 23:03 [PATCH] replace use of word segregate in comments Stephen Hemminger
2024-10-08 9:53 ` Morten Brørup
2024-10-08 15:49 ` [PATCH v2] " Stephen Hemminger
2024-10-09 0:36 ` fengchengwen
2024-11-26 22:58 ` Thomas Monjalon [this message]
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=4856624.jE0xQCEvom@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=mb@smartsharesystems.com \
--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 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.