DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] eal: fix spelling errors
Date: Fri, 24 Apr 2020 18:28:44 +0200	[thread overview]
Message-ID: <16202598.5WZRyvrzyv@thomas> (raw)
In-Reply-To: <20200310163520.9009-1-stephen@networkplumber.org>

10/03/2020 17:35, Stephen Hemminger:
> Fix spelling errors in comments (found with codespell).
> 
> Note that "inbetween" is not correct in English and should
> either be two words or better yet, the in can be dropped.
> https://www.grammarly.com/blog/in-between-or-inbetween/
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>

Applied, thanks




      reply	other threads:[~2020-04-24 16:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10 16:32 [dpdk-dev] [PATCH] " Stephen Hemminger
2020-03-10 16:35 ` [dpdk-dev] [PATCH v2] " Stephen Hemminger
2020-04-24 16:28   ` 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=16202598.5WZRyvrzyv@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    /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).