From: "Kovacevic, Marko" <marko.kovacevic@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: spelling fixes
Date: Mon, 22 Oct 2018 08:52:57 +0000 [thread overview]
Message-ID: <6DC05C7C5F25994B81B3F2F214251F6602039A2E@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <20181018223255.12816-1-stephen@networkplumber.org>
> Trivial pelling errors found by codespell.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
> doc/guides/eventdevs/opdl.rst | 2 +-
> doc/guides/nics/axgbe.rst | 2 +-
> doc/guides/nics/enic.rst | 2 +-
> doc/guides/nics/mvpp2.rst | 2 +-
> doc/guides/nics/virtio.rst | 2 +-
> 5 files changed, 5 insertions(+), 5 deletions(-)
Commit message spelling error, I don't know if it was intentional if it was I like it :)
Even if it wasn't I think it should stay :)
Acked-by: Marko Kovacevic <marko.kovacevic@intel.com>
next prev parent reply other threads:[~2018-10-22 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 22:32 Stephen Hemminger
2018-10-22 8:52 ` Kovacevic, Marko [this message]
2018-10-22 13:48 ` Ferruh Yigit
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=6DC05C7C5F25994B81B3F2F214251F6602039A2E@IRSMSX104.ger.corp.intel.com \
--to=marko.kovacevic@intel.com \
--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).