From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: shreyansh.jain@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw28561 [PATCH v4 34/41] net/dpaa: add support for flow control
Date: 09 Sep 2017 07:10:51 -0700 [thread overview]
Message-ID: <1a8a4b$13i0g4b@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4405 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/28561
_apply patch file failure_
Submitter: Shreyansh Jain <shreyansh.jain@nxp.com>
Date: Sat, 9 Sep 2017 16:51:28 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:85238f501ec36bc6f0e15e6434296312841259bd
Repo:dpdk-next-crypto, Branch:master, CommitID:12f47db9b73e9ea82702b4ab128df20fc9bc0f5f
Repo:dpdk-next-net, Branch:master, CommitID:5362cc7ff322e05ece437375ed19be6db990304d
Repo:dpdk-next-virtio, Branch:master, CommitID:6c157fe64650167646ff1312f9f7e7dc3674d7eb
Repo:dpdk, Branch:master, CommitID:06791a4bcedf3eb97f05c13debff90272e3b0d54
Apply patch file failed:
Repo: dpdk
28561:
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/dpaa.ini b/doc/guides/nics/features/dpaa.ini
|index c09efd8..1ba6b11 100644
|--- a/doc/guides/nics/features/dpaa.ini
|+++ b/doc/guides/nics/features/dpaa.ini
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/dpaa/dpaa_ethdev.c
Hunk #1 succeeded at 133 (offset -196 lines).
Hunk #2 FAILED at 463.
Hunk #3 FAILED at 479.
Hunk #4 FAILED at 632.
3 out of 4 hunks FAILED -- saving rejects to file drivers/net/dpaa/dpaa_ethdev.c.rej
Repo: dpdk-next-crypto
28561:
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/dpaa.ini b/doc/guides/nics/features/dpaa.ini
|index c09efd8..1ba6b11 100644
|--- a/doc/guides/nics/features/dpaa.ini
|+++ b/doc/guides/nics/features/dpaa.ini
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/dpaa/dpaa_ethdev.c
Hunk #1 succeeded at 133 (offset -196 lines).
Hunk #2 FAILED at 463.
Hunk #3 FAILED at 479.
Hunk #4 FAILED at 632.
3 out of 4 hunks FAILED -- saving rejects to file drivers/net/dpaa/dpaa_ethdev.c.rej
Repo: dpdk-next-net
28561:
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/dpaa.ini b/doc/guides/nics/features/dpaa.ini
|index c09efd8..1ba6b11 100644
|--- a/doc/guides/nics/features/dpaa.ini
|+++ b/doc/guides/nics/features/dpaa.ini
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/dpaa/dpaa_ethdev.c
Hunk #1 succeeded at 133 (offset -196 lines).
Hunk #2 FAILED at 463.
Hunk #3 FAILED at 479.
Hunk #4 FAILED at 632.
3 out of 4 hunks FAILED -- saving rejects to file drivers/net/dpaa/dpaa_ethdev.c.rej
Repo: dpdk-next-virtio
28561:
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/dpaa.ini b/doc/guides/nics/features/dpaa.ini
|index c09efd8..1ba6b11 100644
|--- a/doc/guides/nics/features/dpaa.ini
|+++ b/doc/guides/nics/features/dpaa.ini
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/dpaa/dpaa_ethdev.c
Hunk #1 succeeded at 133 (offset -196 lines).
Hunk #2 FAILED at 463.
Hunk #3 FAILED at 479.
Hunk #4 FAILED at 632.
3 out of 4 hunks FAILED -- saving rejects to file drivers/net/dpaa/dpaa_ethdev.c.rej
Repo: dpdk-next-eventdev
28561:
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/dpaa.ini b/doc/guides/nics/features/dpaa.ini
|index c09efd8..1ba6b11 100644
|--- a/doc/guides/nics/features/dpaa.ini
|+++ b/doc/guides/nics/features/dpaa.ini
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/dpaa/dpaa_ethdev.c
Hunk #1 succeeded at 133 (offset -196 lines).
Hunk #2 FAILED at 463.
Hunk #3 FAILED at 479.
Hunk #4 FAILED at 632.
3 out of 4 hunks FAILED -- saving rejects to file drivers/net/dpaa/dpaa_ethdev.c.rej
DPDK STV team
reply other threads:[~2017-09-09 14:10 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='1a8a4b$13i0g4b@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=shreyansh.jain@nxp.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).