From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>, x-fn-spp@sl.ntt-tx.co.jp
Cc: spp@dpdk.org
Subject: Re: [spp] [PATCH v5 0/2] docs:fix error and improve document under spp_vf
Date: Thu, 24 May 2018 13:54:08 +0100 [thread overview]
Message-ID: <2cdfd6e8-6a75-eefc-43b5-f54d58a274ce@intel.com> (raw)
In-Reply-To: <a5f8c76c-ba08-b4da-dd99-3f29d931a362@lab.ntt.co.jp>
On 5/17/2018 10:46 AM, Yasufumi Ogawa wrote:
> On 2018/05/17 17:18, x-fn-spp@sl.ntt-tx.co.jp wrote:
>> From: Hideyuki-Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
>>
>> Hello Yasufumi-san,
>> In v4 patch set I shortened the content too much.
>> The important thing is "commit message should be wrapped at 72 characters".
>>
>> So I reverted commit message with proper wrapping.
>>
>> The purpose of these patch is the same with the original
>> (fix and improve document related to spp_vf).
>>
>> BR,
>> Hideyuki Yamashita
>>
>> Hideyuki-Yamashita (2):
>> docs: fix document error under spp_vf directory
>> docs: improve document under spp_vf directory
> I confirmed that both of your patches are merged without any problem. Your update will be helpful for users. Thanks!
>
> Acked-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Series applied, thanks.
In author name "-" removed: s/Hideyuki-Yamashita/Hideyuki Yamashita/
next prev parent reply other threads:[~2018-05-24 12:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 5:43 [spp] [PATCH 0/2] doc:Fix " x-fn-spp
2018-05-09 6:33 ` Yasufumi Ogawa
2018-05-09 6:57 ` [spp] [PATCH v2 0/2] doc:fix " x-fn-spp
2018-05-16 8:49 ` [spp] [PATCH v3 0/2] docs:fix " x-fn-spp
2018-05-17 4:00 ` Yasufumi Ogawa
2018-05-17 6:41 ` [spp] [PATCH v4 " x-fn-spp
2018-05-17 8:18 ` [spp] [PATCH v5 " x-fn-spp
2018-05-17 9:46 ` Yasufumi Ogawa
2018-05-24 12:54 ` Ferruh Yigit [this message]
2018-05-17 8:18 ` [spp] [PATCH v5 1/2] docs: fix document error under spp_vf directory x-fn-spp
2018-05-17 8:18 ` [spp] [PATCH v5 2/2] docs: improve document " x-fn-spp
2018-05-17 6:41 ` [spp] [PATCH v4 1/2] docs: fix document error " x-fn-spp
2018-05-17 6:41 ` [spp] [PATCH v4 2/2] docs: improve document " x-fn-spp
2018-05-16 8:49 ` [spp] [PATCH v3 1/2] docs: fix document error " x-fn-spp
2018-05-16 8:49 ` [spp] [PATCH v3 2/2] docs: improve document " x-fn-spp
2018-05-09 6:58 ` [spp] [PATCH v2 1/2] docs: fix document error " x-fn-spp
2018-05-11 3:44 ` Yasufumi Ogawa
2018-05-09 6:58 ` [spp] [PATCH v2 2/2] docs: improve document " x-fn-spp
2018-05-11 4:23 ` Yasufumi Ogawa
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=2cdfd6e8-6a75-eefc-43b5-f54d58a274ce@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ogawa.yasufumi@lab.ntt.co.jp \
--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).