From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>,
spp@dpdk.org, nakamura.hiroyuki@po.ntt-tx.co.jp
Subject: Re: [spp] [PATCH 11/28] docs: add config image for spp_vf usercase1
Date: Wed, 7 Feb 2018 15:42:47 +0000 [thread overview]
Message-ID: <bb421739-ceb1-576f-b0e3-9f9e6bb1750b@intel.com> (raw)
In-Reply-To: <afe203d8-e0ae-1280-210d-5754a9439965@lab.ntt.co.jp>
On 2/7/2018 12:10 AM, Yasufumi Ogawa wrote:
> On 2018/02/07 0:34, Ferruh Yigit wrote:
>> On 2/5/2018 2:39 AM, ogawa.yasufumi@lab.ntt.co.jp wrote:
>>> From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
>>>
>>> Add an image of detailed network configuration.
>>
>> Getting error while trying to apply the patch [1], this can be similar issue
>> previously we had in image file.
>>
>> [1]
>> Applying: docs: add config image for spp_vf usercase1
>> error: corrupt patch at line 1930
> Sorry about that, but it is weird because I had sent patches to me and
> checked be merged without any of errors before sent to ML. In addition,
> previous error was caused because of violation for maximum 998 chars
> limits in RFC 2822. Maximum line of my patches is around 500.
>
> I checked patches with sent to spp ML and latest repo again, and merged
> successfully. However, I would like to make and send errored patch.
Copy-paste of new 11/28 worked for me, pushing the set, thanks.
>
>>
>>
>>>
>>> Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
>> <...>
>>
>>
>>
>
>
next prev parent reply other threads:[~2018-02-07 15:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 2:38 [spp] [PATCH 01/28] docs: change doc structure to add spp_vf ogawa.yasufumi
2018-02-05 2:38 ` [spp] [PATCH 02/28] docs: add indexes for spp_vf ogawa.yasufumi
2018-02-05 2:38 ` [spp] [PATCH 03/28] docs: add spp_vf overview ogawa.yasufumi
2018-02-05 2:38 ` [spp] [PATCH 04/28] docs: add spp_vf design section ogawa.yasufumi
2018-02-05 2:38 ` [spp] [PATCH 05/28] docs: add spp_vf gsg section ogawa.yasufumi
2018-02-05 2:38 ` [spp] [PATCH 06/28] docs: add spp_vf explanation section ogawa.yasufumi
2018-02-05 2:39 ` [spp] [PATCH 07/28] docs: add image for sample usage ogawa.yasufumi
2018-02-05 2:39 ` [spp] [PATCH 08/28] docs: fix bug spp_vf howto_use guide ogawa.yasufumi
2018-02-05 2:39 ` [spp] [PATCH 09/28] docs: fix link warning ogawa.yasufumi
2018-02-05 2:39 ` [spp] [PATCH 10/28] docs: add overview image for spp_vf usercase1 ogawa.yasufumi
2018-02-05 2:39 ` [spp] [PATCH 11/28] docs: add config " ogawa.yasufumi
2018-02-06 15:34 ` Ferruh Yigit
2018-02-07 0:10 ` Yasufumi Ogawa
2018-02-07 15:42 ` Ferruh Yigit [this message]
2018-02-07 0:26 ` ogawa.yasufumi
2018-02-05 2:39 ` [spp] [PATCH 12/28] docs: add numref attribute for sphinx ogawa.yasufumi
2018-02-05 2:39 ` [spp] [PATCH 13/28] docs: add usecase section in spp_vf ogawa.yasufumi
2018-02-05 2:39 ` [spp] [PATCH 14/28] docs: add ssh login usecase for spp_vf ogawa.yasufumi
2018-02-05 2:39 ` [spp] [PATCH 15/28] docs: add labels for using sphinx ref directive ogawa.yasufumi
2018-02-05 2:39 ` [spp] [PATCH 16/28] docs: update spp_vf overview image ogawa.yasufumi
2018-02-05 2:39 ` [spp] [PATCH 17/28] docs: update spp_vf command index ogawa.yasufumi
2018-02-05 2:39 ` [spp] [PATCH 18/28] docs: add spp_vf primary command section ogawa.yasufumi
2018-02-05 2:39 ` [spp] [PATCH 19/28] docs: add spp_vf secondary " ogawa.yasufumi
2018-02-05 2:39 ` [spp] [PATCH 20/28] docs: add spp_vf common " ogawa.yasufumi
2018-02-05 2:39 ` [spp] [PATCH 21/28] docs: fix bug spp_vf command index ogawa.yasufumi
2018-02-07 15:44 ` [spp] [PATCH 01/28] docs: change doc structure to add spp_vf 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=bb421739-ceb1-576f-b0e3-9f9e6bb1750b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=nakamura.hiroyuki@po.ntt-tx.co.jp \
--cc=ogawa.yasufumi@lab.ntt.co.jp \
--cc=spp@dpdk.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).