From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: pascal.mazon@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw21797 [PATCH v5 4/8] net/tap: add MTU management
Date: 15 Mar 2017 11:27:29 -0700 [thread overview]
Message-ID: <ffb989$1pvue2@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4371 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/21797
_apply patch file failure_
Submitter: Pascal Mazon <pascal.mazon@6wind.com>
Date: Wed, 15 Mar 2017 15:48:15 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:acd3b86bf98694fc5d418092edb740145d8214e1
Repo:dpdk-next-crypto, Branch:master, CommitID:6254e326fb9b1bce6dcbb1391c8d9a0cb5e864c2
Repo:dpdk-next-net, Branch:master, CommitID:1ab145a44f7822d05d4edb9398ae3c19c9c46b55
Repo:dpdk-next-virtio, Branch:master, CommitID:14d3a8536b51f9c1e7d65bcf536b5b348ead1ec1
Repo:dpdk, Branch:master, CommitID:d89a5bce1d20068035da613c455d1612c20eec5e
Apply patch file failed:
Repo: dpdk
21797:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/doc/guides/nics/features/tap.ini b/doc/guides/nics/features/tap.ini
|index d9b47a003654..b80577753240 100644
|--- a/doc/guides/nics/features/tap.ini
|+++ b/doc/guides/nics/features/tap.ini
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 350.
Hunk #2 succeeded at 524 (offset -71 lines).
Hunk #3 succeeded at 628 (offset -72 lines).
Hunk #4 FAILED at 732.
Hunk #5 succeeded at 699 (offset -83 lines).
2 out of 5 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
Repo: dpdk-next-crypto
21797:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/doc/guides/nics/features/tap.ini b/doc/guides/nics/features/tap.ini
|index d9b47a003654..b80577753240 100644
|--- a/doc/guides/nics/features/tap.ini
|+++ b/doc/guides/nics/features/tap.ini
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 350.
Hunk #2 succeeded at 524 (offset -71 lines).
Hunk #3 succeeded at 628 (offset -72 lines).
Hunk #4 FAILED at 732.
Hunk #5 succeeded at 699 (offset -83 lines).
2 out of 5 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
Repo: dpdk-next-net
21797:
patching file doc/guides/nics/features/tap.ini
Hunk #1 FAILED at 9.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/nics/features/tap.ini.rej
patching file drivers/net/tap/rte_eth_tap.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
5 out of 5 hunks ignored -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
Repo: dpdk-next-virtio
21797:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/doc/guides/nics/features/tap.ini b/doc/guides/nics/features/tap.ini
|index d9b47a003654..b80577753240 100644
|--- a/doc/guides/nics/features/tap.ini
|+++ b/doc/guides/nics/features/tap.ini
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 350.
Hunk #2 succeeded at 524 (offset -71 lines).
Hunk #3 succeeded at 628 (offset -72 lines).
Hunk #4 FAILED at 732.
Hunk #5 succeeded at 699 (offset -83 lines).
2 out of 5 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
Repo: dpdk-next-eventdev
21797:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/doc/guides/nics/features/tap.ini b/doc/guides/nics/features/tap.ini
|index d9b47a003654..b80577753240 100644
|--- a/doc/guides/nics/features/tap.ini
|+++ b/doc/guides/nics/features/tap.ini
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 350.
Hunk #2 succeeded at 524 (offset -71 lines).
Hunk #3 succeeded at 628 (offset -72 lines).
Hunk #4 FAILED at 732.
Hunk #5 succeeded at 699 (offset -83 lines).
2 out of 5 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
DPDK STV team
reply other threads:[~2017-03-15 18:27 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='ffb989$1pvue2@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=pascal.mazon@6wind.com \
--cc=test-report@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).