patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thierry Herbelot <thierry.herbelot@6wind.com>, dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>, stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] doc/guides/nics: fix typos
Date: Fri, 18 Oct 2019 17:29:06 +0100	[thread overview]
Message-ID: <e853dd40-f607-002a-2a82-a8eb8560a3b6@intel.com> (raw)
In-Reply-To: <20191018150657.17600-1-thierry.herbelot@6wind.com>

On 10/18/2019 4:06 PM, Thierry Herbelot wrote:
> 'CRC striping' should be spelled 'CRC stripping'.
> 
> Fixes: 3eee1f067e7c ('fm10k: add guide')
> Fixes: 7a4d9f6676d7 ('doc: add liquidio')
> Fixes: f820b5896631 ('doc: add octeontx ethdev driver documentation')
> Fixes: 920717e4d8ba ('net/octeontx2: add device start operation')
> Fixes: f994cecafdcf ('doc: add ThunderX nicvf')
> Cc: stable@dpdk.org
> 
> Signed-off-by: Thierry Herbelot <thierry.herbelot@6wind.com>

Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2019-10-18 16:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 15:06 [dpdk-stable] " Thierry Herbelot
2019-10-18 16:29 ` Ferruh Yigit [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=e853dd40-f607-002a-2a82-a8eb8560a3b6@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=thierry.herbelot@6wind.com \
    --cc=thomas@monjalon.net \
    /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).