From: Stephen Hemminger <stephen@networkplumber.org>
To: Luca Boccassi <bluca@debian.org>
Cc: dev@dpdk.org, Shepard Siegel <shepard.siegel@atomicrules.com>,
Ed Czeck <ed.czeck@atomicrules.com>,
John Miller <john.miller@atomicrules.com>
Subject: Re: [PATCH] doc/ark: replace word segregation
Date: Mon, 3 Apr 2023 19:15:35 -0700 [thread overview]
Message-ID: <20230403191535.220b14b2@hermes.local> (raw)
In-Reply-To: <CAMw=ZnTT0=U0j+-=cemCLTKpoS6qnDTGnHFEukePOGPGf4e_4Q@mail.gmail.com>
On Tue, 4 Apr 2023 00:06:16 +0100
Luca Boccassi <bluca@debian.org> wrote:
> > * Dynamic per-queue MBUF (re)sizing up to 32KB
> > -* SR-IOV, VF-based queue-segregation
> > +* SR-IOV, VF-based queue-seperation
>
> Did you mean 'separation' by any chance
Yup. It is one of the words I always misspell...
prev parent reply other threads:[~2023-04-04 2:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 22:53 Stephen Hemminger
2023-04-03 5:31 ` Tyler Retzlaff
2023-05-17 18:31 ` Ferruh Yigit
2023-04-03 23:06 ` Luca Boccassi
2023-04-04 2:15 ` Stephen Hemminger [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=20230403191535.220b14b2@hermes.local \
--to=stephen@networkplumber.org \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ed.czeck@atomicrules.com \
--cc=john.miller@atomicrules.com \
--cc=shepard.siegel@atomicrules.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).