From: sys_stv@intel.com
To: test-report@dpdk.org,zhe.tao@intel.com
Subject: [dpdk-test-report] |ERROR| pw 8401 [dpdk-dev, 4/4, v4] add RX and TX selection function for FVL
Date: 31 Oct 2015 11:30:57 -0700 [thread overview]
Message-ID: <edcf24$hk85s0@FMSMGA003.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1551 bytes --]
Test-Status: Malformed patch
Submitter: Zhe Tao <zhe.tao@intel.com>
Date: Fri, 30 Oct 2015 22:16:38 +0800
DPDK git baseline: affc455438f4cbd3b14e2d9a24fbc154e22d68d3
Malformed PatchworkID:
http://www.dpdk.org/dev/patchwork/patch/8401/
Error: patching file doc/guides/rel_notes/release_2_2.rst
patching file drivers/net/i40e/i40e_ethdev.c
patching file drivers/net/i40e/i40e_ethdev.h
patching file drivers/net/i40e/i40e_ethdev_vf.c
patching file drivers/net/i40e/i40e_rxtx.c
Hunk #1 succeeded at 2108 (offset 3 lines).
Hunk #2 succeeded at 2218 (offset 3 lines).
Hunk #3 succeeded at 2231 (offset 3 lines).
Hunk #4 succeeded at 2493 (offset 3 lines).
Hunk #5 succeeded at 2562 (offset 3 lines).
Hunk #8 FAILED at 3063.
Hunk #9 FAILED at 3088.
Hunk #10 succeeded at 3062 with fuzz 2 (offset -39 lines).
2 out of 10 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_rxtx.c.rej
patching file drivers/net/i40e/i40e_rxtx.h
Hunk #1 succeeded at 113 (offset -19 lines).
Hunk #2 FAILED at 235.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_rxtx.h.rej
can't find file to patch at input line 456
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/i40e/i40e_rxtx_vec.c b/drivers/net/i40e/i40e_rxtx_vec.c
|index f746209..047aff5 100644
|--- a/drivers/net/i40e/i40e_rxtx_vec.c
|+++ b/drivers/net/i40e/i40e_rxtx_vec.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
DPDK STV team
reply other threads:[~2015-10-31 18:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='edcf24$hk85s0@FMSMGA003.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=zhe.tao@intel.com \
/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).