From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: pascal.mazon@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw22073 [PATCH v6 2/4] net/tap: add preliminary support for rte_flow
Date: 22 Mar 2017 07:59:54 -0700 [thread overview]
Message-ID: <ffb989$1sn2o1@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 7425 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/22073
_apply patch file failure_
Submitter: Pascal Mazon <pascal.mazon@6wind.com>
Date: Wed, 22 Mar 2017 10:48:19 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:acd3b86bf98694fc5d418092edb740145d8214e1
Repo:dpdk-next-crypto, Branch:master, CommitID:8482641f7301db78d585dc02c9fc5790d380b1b5
Repo:dpdk-next-net, Branch:master, CommitID:8e261a821747d426c4138496aaf356458db0c3b7
Repo:dpdk-next-virtio, Branch:master, CommitID:aabbe1bcc182e8baa949e4d0a63f77296a2bad69
Repo:dpdk, Branch:master, CommitID:84aac97b49994be6b461b46be160b47938e697b3
Apply patch file failed:
Repo: dpdk
22073:
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 a51712dce066..9d73f61cca3b 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/Makefile
Hunk #1 succeeded at 46 (offset -1 lines).
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 56.
Hunk #2 succeeded at 428 (offset -54 lines).
Hunk #3 FAILED at 807.
Hunk #4 succeeded at 700 (offset -178 lines).
Hunk #5 succeeded at 815 (offset -178 lines).
2 out of 5 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 74
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/rte_eth_tap.h b/drivers/net/tap/rte_eth_tap.h
|index aafdef1faa99..bf8226736627 100644
|--- a/drivers/net/tap/rte_eth_tap.h
|+++ b/drivers/net/tap/rte_eth_tap.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/net/tap/tap_flow.c
patching file drivers/net/tap/tap_flow.h
Repo: dpdk-next-crypto
22073:
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 a51712dce066..9d73f61cca3b 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/Makefile
Hunk #1 succeeded at 46 (offset -1 lines).
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 56.
Hunk #2 succeeded at 428 (offset -54 lines).
Hunk #3 FAILED at 807.
Hunk #4 succeeded at 700 (offset -178 lines).
Hunk #5 succeeded at 815 (offset -178 lines).
2 out of 5 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 74
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/rte_eth_tap.h b/drivers/net/tap/rte_eth_tap.h
|index aafdef1faa99..bf8226736627 100644
|--- a/drivers/net/tap/rte_eth_tap.h
|+++ b/drivers/net/tap/rte_eth_tap.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/net/tap/tap_flow.c
patching file drivers/net/tap/tap_flow.h
Repo: dpdk-next-net
22073:
patching file doc/guides/nics/features/tap.ini
patching file drivers/net/tap/Makefile
Hunk #1 succeeded at 46 (offset -1 lines).
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 56.
Hunk #2 succeeded at 514 (offset 32 lines).
Hunk #3 succeeded at 839 (offset 32 lines).
Hunk #4 succeeded at 911 (offset 32 lines).
Hunk #5 succeeded at 1026 (offset 32 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 74
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/rte_eth_tap.h b/drivers/net/tap/rte_eth_tap.h
|index aafdef1faa99..bf8226736627 100644
|--- a/drivers/net/tap/rte_eth_tap.h
|+++ b/drivers/net/tap/rte_eth_tap.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/net/tap/tap_flow.c
patching file drivers/net/tap/tap_flow.h
Repo: dpdk-next-virtio
22073:
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 a51712dce066..9d73f61cca3b 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/Makefile
Hunk #1 succeeded at 46 (offset -1 lines).
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 56.
Hunk #2 succeeded at 428 (offset -54 lines).
Hunk #3 FAILED at 807.
Hunk #4 succeeded at 700 (offset -178 lines).
Hunk #5 succeeded at 815 (offset -178 lines).
2 out of 5 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 74
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/rte_eth_tap.h b/drivers/net/tap/rte_eth_tap.h
|index aafdef1faa99..bf8226736627 100644
|--- a/drivers/net/tap/rte_eth_tap.h
|+++ b/drivers/net/tap/rte_eth_tap.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/net/tap/tap_flow.c
patching file drivers/net/tap/tap_flow.h
Repo: dpdk-next-eventdev
22073:
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 a51712dce066..9d73f61cca3b 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/Makefile
Hunk #1 succeeded at 46 (offset -1 lines).
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 56.
Hunk #2 succeeded at 428 (offset -54 lines).
Hunk #3 FAILED at 807.
Hunk #4 succeeded at 700 (offset -178 lines).
Hunk #5 succeeded at 815 (offset -178 lines).
2 out of 5 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 74
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/rte_eth_tap.h b/drivers/net/tap/rte_eth_tap.h
|index aafdef1faa99..bf8226736627 100644
|--- a/drivers/net/tap/rte_eth_tap.h
|+++ b/drivers/net/tap/rte_eth_tap.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/net/tap/tap_flow.c
patching file drivers/net/tap/tap_flow.h
DPDK STV team
reply other threads:[~2017-03-22 14:59 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$1sn2o1@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).