From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rami Rosen <ramirose@gmail.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: fix spelling in testpmd guide
Date: Fri, 12 Apr 2019 17:58:09 +0100 [thread overview]
Message-ID: <8cf46b78-6eb1-8abb-0cb5-1f2d827264d4@intel.com> (raw)
Message-ID: <20190412165809.UcGUPIs21w-QkQe5TPn9xVeqlT3FW7P0rqpdKhZM-nI@z> (raw)
In-Reply-To: <CAHLOa7QPFPmSxE93a9NooYejZQPgnTQp_moYBkrQ+eyvytq7XQ@mail.gmail.com>
On 4/10/2019 11:04 PM, Rami Rosen wrote:
> Stephen Hemminger <stephen@networkplumber.org>:
>
>> Minor spelling errors found with aspell.
>>
>> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>> --
>>
> Acked-by: Rami Rosen <ramirose@gmail.com>
>
Fixes: e76d7a768ce0 ("doc: fix syntax in testpmd user guide")
Fixes: fb73e096110a ("app/testpmd: enable device hotplug monitoring")
Cc: stable@dpdk.org
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2019-04-12 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 17:48 Stephen Hemminger
2019-04-10 17:48 ` Stephen Hemminger
2019-04-10 22:04 ` Rami Rosen
2019-04-10 22:04 ` Rami Rosen
2019-04-12 16:58 ` Ferruh Yigit [this message]
2019-04-12 16:58 ` 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=8cf46b78-6eb1-8abb-0cb5-1f2d827264d4@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=ramirose@gmail.com \
--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).