From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: jia.guo@intel.com
Subject: [dpdk-test-report] |FAILURE| pw36979 [PATCH V18 4/5] eal: add driver auto bind for hot insertion
Date: 11 Apr 2018 02:50:07 -0700 [thread overview]
Message-ID: <0590c7$1cp47h@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 7753 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/36979
_apply patch file failure_
Submitter: Guo Jia <jia.guo@intel.com>
Date: Wed, 4 Apr 2018 02:17:19 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:8cafb78bb4d7a724c41aefc326d9eae79c6fb6e7
Repo:dpdk-next-crypto, Branch:master, CommitID:28adae99e7b19063b6f18b6f0371495fc9bd59bc
Repo:dpdk-next-net, Branch:master, CommitID:03315a784aeb337e55f5859b3624cfb006ae0cc6
Repo:dpdk-next-virtio, Branch:master, CommitID:6c7026928154594b62348b7c56ed36317b19812e
Repo:dpdk, Branch:master, CommitID:bef5a2d629d536a82c81c02b84684da828c0e37f
Apply patch file failed:
Repo: dpdk
36979:
patching file doc/guides/rel_notes/release_18_05.rst
Hunk #1 succeeded at 59 with fuzz 2 (offset 8 lines).
can't find file to patch at input line 25
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_eal/bsdapp/eal/eal_dev.c b/lib/librte_eal/bsdapp/eal/eal_dev.c
|index 1c6c51b..e953a87 100644
|--- a/lib/librte_eal/bsdapp/eal/eal_dev.c
|+++ b/lib/librte_eal/bsdapp/eal/eal_dev.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file lib/librte_eal/common/include/rte_dev.h
Hunk #1 FAILED at 380.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/include/rte_dev.h.rej
can't find file to patch at input line 65
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_eal/linuxapp/eal/eal_dev.c b/lib/librte_eal/linuxapp/eal/eal_dev.c
|index fabb37a..eb8275f 100644
|--- a/lib/librte_eal/linuxapp/eal/eal_dev.c
|+++ b/lib/librte_eal/linuxapp/eal/eal_dev.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 263.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej
Repo: dpdk-next-crypto
36979:
patching file doc/guides/rel_notes/release_18_05.rst
Hunk #1 succeeded at 78 with fuzz 2 (offset 27 lines).
can't find file to patch at input line 25
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_eal/bsdapp/eal/eal_dev.c b/lib/librte_eal/bsdapp/eal/eal_dev.c
|index 1c6c51b..e953a87 100644
|--- a/lib/librte_eal/bsdapp/eal/eal_dev.c
|+++ b/lib/librte_eal/bsdapp/eal/eal_dev.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file lib/librte_eal/common/include/rte_dev.h
Hunk #1 FAILED at 380.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/include/rte_dev.h.rej
can't find file to patch at input line 65
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_eal/linuxapp/eal/eal_dev.c b/lib/librte_eal/linuxapp/eal/eal_dev.c
|index fabb37a..eb8275f 100644
|--- a/lib/librte_eal/linuxapp/eal/eal_dev.c
|+++ b/lib/librte_eal/linuxapp/eal/eal_dev.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 263.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej
Repo: dpdk-next-net
36979:
patching file doc/guides/rel_notes/release_18_05.rst
Hunk #1 succeeded at 70 with fuzz 2 (offset 19 lines).
can't find file to patch at input line 25
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_eal/bsdapp/eal/eal_dev.c b/lib/librte_eal/bsdapp/eal/eal_dev.c
|index 1c6c51b..e953a87 100644
|--- a/lib/librte_eal/bsdapp/eal/eal_dev.c
|+++ b/lib/librte_eal/bsdapp/eal/eal_dev.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file lib/librte_eal/common/include/rte_dev.h
Hunk #1 FAILED at 380.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/include/rte_dev.h.rej
can't find file to patch at input line 65
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_eal/linuxapp/eal/eal_dev.c b/lib/librte_eal/linuxapp/eal/eal_dev.c
|index fabb37a..eb8275f 100644
|--- a/lib/librte_eal/linuxapp/eal/eal_dev.c
|+++ b/lib/librte_eal/linuxapp/eal/eal_dev.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 263.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej
Repo: dpdk-next-virtio
36979:
patching file doc/guides/rel_notes/release_18_05.rst
Hunk #1 succeeded at 71 with fuzz 2 (offset 20 lines).
can't find file to patch at input line 25
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_eal/bsdapp/eal/eal_dev.c b/lib/librte_eal/bsdapp/eal/eal_dev.c
|index 1c6c51b..e953a87 100644
|--- a/lib/librte_eal/bsdapp/eal/eal_dev.c
|+++ b/lib/librte_eal/bsdapp/eal/eal_dev.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file lib/librte_eal/common/include/rte_dev.h
Hunk #1 FAILED at 380.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/include/rte_dev.h.rej
can't find file to patch at input line 65
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_eal/linuxapp/eal/eal_dev.c b/lib/librte_eal/linuxapp/eal/eal_dev.c
|index fabb37a..eb8275f 100644
|--- a/lib/librte_eal/linuxapp/eal/eal_dev.c
|+++ b/lib/librte_eal/linuxapp/eal/eal_dev.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 263.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej
Repo: dpdk-next-eventdev
36979:
patching file doc/guides/rel_notes/release_18_05.rst
Hunk #1 succeeded at 65 with fuzz 2 (offset 14 lines).
can't find file to patch at input line 25
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_eal/bsdapp/eal/eal_dev.c b/lib/librte_eal/bsdapp/eal/eal_dev.c
|index 1c6c51b..e953a87 100644
|--- a/lib/librte_eal/bsdapp/eal/eal_dev.c
|+++ b/lib/librte_eal/bsdapp/eal/eal_dev.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file lib/librte_eal/common/include/rte_dev.h
Hunk #1 FAILED at 380.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/include/rte_dev.h.rej
can't find file to patch at input line 65
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_eal/linuxapp/eal/eal_dev.c b/lib/librte_eal/linuxapp/eal/eal_dev.c
|index fabb37a..eb8275f 100644
|--- a/lib/librte_eal/linuxapp/eal/eal_dev.c
|+++ b/lib/librte_eal/linuxapp/eal/eal_dev.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 263.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej
DPDK STV team
reply other threads:[~2018-04-11 9:50 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='0590c7$1cp47h@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=jia.guo@intel.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).