From: Ferruh Yigit <ferruh.yigit@intel.com>
To: x-fn-spp@sl.ntt-tx.co.jp, spp@dpdk.org
Subject: Re: [spp] [PATCH 1/2] doc: Fix document error under spp_vf directory
Date: Thu, 24 May 2018 13:49:51 +0100 [thread overview]
Message-ID: <54eb9526-d049-ec28-636f-81dd81156661@intel.com> (raw)
In-Reply-To: <627ec749-2bcc-6c94-826c-c945eef7e7e5@intel.com>
On 5/24/2018 1:47 PM, Ferruh Yigit wrote:
> On 5/9/2018 6:45 AM, x-fn-spp@sl.ntt-tx.co.jp wrote:
>> From: Hideyuki-Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
>>
>> - Fix typo in build.rst
>> - Fix typo and error in usecase1.rst
>>
>> Signed-off-by: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
>> Signed-off-by: Naoki Takada <takada.naoki@lab.ntt.co.jp>
>
> Series applied, thanks.
My bad, new version is available, will drop this one.
next prev parent reply other threads:[~2018-05-24 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1525844601-26319-1-git-send-email-x-fn-spp@sl.ntt-tx.co.jp>
2018-05-09 5:45 ` x-fn-spp
2018-05-24 12:47 ` Ferruh Yigit
2018-05-24 12:49 ` Ferruh Yigit [this message]
2018-05-09 5:45 ` [spp] [PATCH 2/2] doc: Improve document " x-fn-spp
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=54eb9526-d049-ec28-636f-81dd81156661@intel.com \
--to=ferruh.yigit@intel.com \
--cc=spp@dpdk.org \
--cc=x-fn-spp@sl.ntt-tx.co.jp \
/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).