From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: pascal.mazon@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw21279 [PATCH 2/4] net/tap: add preliminary support for rte_flow
Date: 06 Mar 2017 07:23:16 -0800 [thread overview]
Message-ID: <63cbe6$11tq3fm@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 7130 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/21279
_apply patch file failure_
Submitter: Pascal Mazon <pascal.mazon@6wind.com>
Date: Fri, 3 Mar 2017 11:45:55 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:720dbd63fd5083f8cacd6c59aa3f2651121d562a
Repo:dpdk-next-crypto, Branch:master, CommitID:c75412f8bbcf24377f51bee8159daf3fea883f1d
Repo:dpdk-next-net, Branch:master, CommitID:e9aef1054c8cae9979cf53c368d95770b0720ed3
Repo:dpdk-next-virtio, Branch:master, CommitID:14d3a8536b51f9c1e7d65bcf536b5b348ead1ec1
Repo:dpdk, Branch:master, CommitID:cf75514c8e2eac82261be0dc0a5e82e9f2653ca8
Apply patch file failed:
Repo: dpdk
21279:
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 52.
Hunk #2 FAILED at 788.
Hunk #3 succeeded at 699 (offset -151 lines).
Hunk #4 succeeded at 813 (offset -151 lines).
2 out of 4 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 67
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap.h b/drivers/net/tap/tap.h
|index 88f62b895feb..323f5705a324 100644
|--- a/drivers/net/tap/tap.h
|+++ b/drivers/net/tap/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
21279:
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 52.
Hunk #2 FAILED at 788.
Hunk #3 succeeded at 699 (offset -151 lines).
Hunk #4 succeeded at 813 (offset -151 lines).
2 out of 4 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 67
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap.h b/drivers/net/tap/tap.h
|index 88f62b895feb..323f5705a324 100644
|--- a/drivers/net/tap/tap.h
|+++ b/drivers/net/tap/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
21279:
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/Makefile
Hunk #1 succeeded at 46 (offset -1 lines).
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 52.
Hunk #2 FAILED at 788.
Hunk #3 succeeded at 699 (offset -151 lines).
Hunk #4 succeeded at 813 (offset -151 lines).
2 out of 4 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 67
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap.h b/drivers/net/tap/tap.h
|index 88f62b895feb..323f5705a324 100644
|--- a/drivers/net/tap/tap.h
|+++ b/drivers/net/tap/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
21279:
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 52.
Hunk #2 FAILED at 788.
Hunk #3 succeeded at 699 (offset -151 lines).
Hunk #4 succeeded at 813 (offset -151 lines).
2 out of 4 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 67
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap.h b/drivers/net/tap/tap.h
|index 88f62b895feb..323f5705a324 100644
|--- a/drivers/net/tap/tap.h
|+++ b/drivers/net/tap/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
21279:
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 52.
Hunk #2 FAILED at 788.
Hunk #3 succeeded at 699 (offset -151 lines).
Hunk #4 succeeded at 813 (offset -151 lines).
2 out of 4 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
can't find file to patch at input line 67
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/tap/tap.h b/drivers/net/tap/tap.h
|index 88f62b895feb..323f5705a324 100644
|--- a/drivers/net/tap/tap.h
|+++ b/drivers/net/tap/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-06 15:23 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='63cbe6$11tq3fm@fmsmga002.fm.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).