From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: wenzhuo.lu@intel.com
Subject: [dpdk-test-report] |FAILURE| pw33039 [PATCH v5 04/14] net/avf: enable basic Rx Tx func
Date: 14 Jan 2018 06:34:29 -0800 [thread overview]
Message-ID: <a797f1$kqkfl@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5679 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/33039
_apply patch file failure_
Submitter: Wenzhuo Lu <wenzhuo.lu@intel.com>
Date: Mon, 8 Jan 2018 13:13:29 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:18280212534a7dcb61021393afd7394eaa1ff51e
Repo:dpdk-next-crypto, Branch:master, CommitID:8da73c32eb2cc4afc2d56a8db09a6ed30f1064c7
Repo:dpdk-next-net, Branch:master, CommitID:d33a340f42d6b7b664409b572f85707a696fcebc
Repo:dpdk-next-virtio, Branch:master, CommitID:814339ba7eea13d132508af2cccec2f73568e2d0
Repo:dpdk, Branch:master, CommitID:f477a4696572201cf26534c83a42ec7dc8098fd8
Apply patch file failed:
Repo: dpdk
33039:
patching file MAINTAINERS
Hunk #1 FAILED at 430.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file config/common_base
patching file doc/guides/nics/features/avf.ini
patching file drivers/net/avf/Makefile
patching file drivers/net/avf/avf_ethdev.c
can't find file to patch at input line 152
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/avf/avf_log.h b/drivers/net/avf/avf_log.h
|index e3f106b..8d574d3 100644
|--- a/drivers/net/avf/avf_log.h
|+++ b/drivers/net/avf/avf_log.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/avf/avf_rxtx.c
patching file drivers/net/avf/avf_rxtx.h
Repo: dpdk-next-crypto
33039:
patching file MAINTAINERS
Hunk #1 FAILED at 430.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file config/common_base
patching file doc/guides/nics/features/avf.ini
patching file drivers/net/avf/Makefile
patching file drivers/net/avf/avf_ethdev.c
can't find file to patch at input line 152
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/avf/avf_log.h b/drivers/net/avf/avf_log.h
|index e3f106b..8d574d3 100644
|--- a/drivers/net/avf/avf_log.h
|+++ b/drivers/net/avf/avf_log.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/avf/avf_rxtx.c
patching file drivers/net/avf/avf_rxtx.h
Repo: dpdk-next-net
33039:
patching file MAINTAINERS
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file MAINTAINERS.rej
patching file config/common_base
Hunk #1 succeeded at 231 (offset 2 lines).
The next patch would create the file doc/guides/nics/features/avf.ini,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/avf/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/net/avf/Makefile.rej
patching file drivers/net/avf/avf_ethdev.c
Hunk #1 FAILED at 39.
Hunk #2 FAILED at 53.
Hunk #3 FAILED at 204.
Hunk #4 succeeded at 1044 with fuzz 1 (offset 637 lines).
Hunk #5 FAILED at 573.
4 out of 5 hunks FAILED -- saving rejects to file drivers/net/avf/avf_ethdev.c.rej
patching file drivers/net/avf/avf_log.h
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/net/avf/avf_log.h.rej
patching file drivers/net/avf/avf_rxtx.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file drivers/net/avf/avf_rxtx.c.rej
patching file drivers/net/avf/avf_rxtx.h
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
4 out of 4 hunks ignored -- saving rejects to file drivers/net/avf/avf_rxtx.h.rej
Repo: dpdk-next-virtio
33039:
patching file MAINTAINERS
Hunk #1 FAILED at 430.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file config/common_base
Hunk #1 succeeded at 222 (offset -7 lines).
patching file doc/guides/nics/features/avf.ini
patching file drivers/net/avf/Makefile
patching file drivers/net/avf/avf_ethdev.c
can't find file to patch at input line 152
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/avf/avf_log.h b/drivers/net/avf/avf_log.h
|index e3f106b..8d574d3 100644
|--- a/drivers/net/avf/avf_log.h
|+++ b/drivers/net/avf/avf_log.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/avf/avf_rxtx.c
patching file drivers/net/avf/avf_rxtx.h
Repo: dpdk-next-eventdev
33039:
patching file MAINTAINERS
Hunk #1 FAILED at 430.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file config/common_base
patching file doc/guides/nics/features/avf.ini
patching file drivers/net/avf/Makefile
patching file drivers/net/avf/avf_ethdev.c
can't find file to patch at input line 152
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/avf/avf_log.h b/drivers/net/avf/avf_log.h
|index e3f106b..8d574d3 100644
|--- a/drivers/net/avf/avf_log.h
|+++ b/drivers/net/avf/avf_log.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/avf/avf_rxtx.c
patching file drivers/net/avf/avf_rxtx.h
DPDK STV team
reply other threads:[~2018-01-14 14:34 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='a797f1$kqkfl@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=wenzhuo.lu@intel.com \
/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).