From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: matan@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw29525 [PATCH v2 4/6] net/mlx4: get back Tx checksum offloads
Date: 03 Oct 2017 04:50:34 -0700 [thread overview]
Message-ID: <7327ef$47heg2@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 9582 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/29525
_apply patch file failure_
Submitter: Matan Azrad <matan@mellanox.com>
Date: Tue, 3 Oct 2017 10:48:29 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:b4b3260b63d2d8d76ff1c66ab4b70e6d1b6a4bbe
Repo:dpdk-next-crypto, Branch:master, CommitID:51c8fe28d6f6c7329c86a695afc5c7def741fe94
Repo:dpdk-next-net, Branch:master, CommitID:58029fee1909059b16383a92451c9cf0f3669630
Repo:dpdk-next-virtio, Branch:master, CommitID:fee08fe0d67d46639d25c201738d9b1b867e443c
Repo:dpdk, Branch:master, CommitID:f0dab530f41689651192cebd7683cddbfc9991e2
Apply patch file failed:
Repo: dpdk
29525:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 397.
Hunk #2 succeeded at 6127 with fuzz 2 (offset 5671 lines).
Hunk #3 succeeded at 6293 with fuzz 2 (offset 5761 lines).
1 out of 3 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 93.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
can't find file to patch at input line 52
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_ethdev.c b/drivers/net/mlx4/mlx4_ethdev.c
|index a9e8059..95cc6e4 100644
|--- a/drivers/net/mlx4/mlx4_ethdev.c
|+++ b/drivers/net/mlx4/mlx4_ethdev.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/mlx4/mlx4_prm.h
can't find file to patch at input line 82
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxtx.c b/drivers/net/mlx4/mlx4_rxtx.c
|index 4200716..2757aec 100644
|--- a/drivers/net/mlx4/mlx4_rxtx.c
|+++ b/drivers/net/mlx4/mlx4_rxtx.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 120
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxtx.h b/drivers/net/mlx4/mlx4_rxtx.h
|index 1b90533..dc283e1 100644
|--- a/drivers/net/mlx4/mlx4_rxtx.h
|+++ b/drivers/net/mlx4/mlx4_rxtx.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 133
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_txq.c b/drivers/net/mlx4/mlx4_txq.c
|index 9333311..2d776eb 100644
|--- a/drivers/net/mlx4/mlx4_txq.c
|+++ b/drivers/net/mlx4/mlx4_txq.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk-next-crypto
29525:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 397.
Hunk #2 succeeded at 6127 with fuzz 2 (offset 5671 lines).
Hunk #3 succeeded at 6293 with fuzz 2 (offset 5761 lines).
1 out of 3 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 93.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
can't find file to patch at input line 52
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_ethdev.c b/drivers/net/mlx4/mlx4_ethdev.c
|index a9e8059..95cc6e4 100644
|--- a/drivers/net/mlx4/mlx4_ethdev.c
|+++ b/drivers/net/mlx4/mlx4_ethdev.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/mlx4/mlx4_prm.h
can't find file to patch at input line 82
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxtx.c b/drivers/net/mlx4/mlx4_rxtx.c
|index 4200716..2757aec 100644
|--- a/drivers/net/mlx4/mlx4_rxtx.c
|+++ b/drivers/net/mlx4/mlx4_rxtx.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 120
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxtx.h b/drivers/net/mlx4/mlx4_rxtx.h
|index 1b90533..dc283e1 100644
|--- a/drivers/net/mlx4/mlx4_rxtx.h
|+++ b/drivers/net/mlx4/mlx4_rxtx.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 133
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_txq.c b/drivers/net/mlx4/mlx4_txq.c
|index 9333311..2d776eb 100644
|--- a/drivers/net/mlx4/mlx4_txq.c
|+++ b/drivers/net/mlx4/mlx4_txq.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk-next-virtio
29525:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 397.
Hunk #2 succeeded at 6127 with fuzz 2 (offset 5671 lines).
Hunk #3 succeeded at 6293 with fuzz 2 (offset 5761 lines).
1 out of 3 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 93.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
can't find file to patch at input line 52
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_ethdev.c b/drivers/net/mlx4/mlx4_ethdev.c
|index a9e8059..95cc6e4 100644
|--- a/drivers/net/mlx4/mlx4_ethdev.c
|+++ b/drivers/net/mlx4/mlx4_ethdev.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/mlx4/mlx4_prm.h
can't find file to patch at input line 82
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxtx.c b/drivers/net/mlx4/mlx4_rxtx.c
|index 4200716..2757aec 100644
|--- a/drivers/net/mlx4/mlx4_rxtx.c
|+++ b/drivers/net/mlx4/mlx4_rxtx.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 120
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxtx.h b/drivers/net/mlx4/mlx4_rxtx.h
|index 1b90533..dc283e1 100644
|--- a/drivers/net/mlx4/mlx4_rxtx.h
|+++ b/drivers/net/mlx4/mlx4_rxtx.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 133
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_txq.c b/drivers/net/mlx4/mlx4_txq.c
|index 9333311..2d776eb 100644
|--- a/drivers/net/mlx4/mlx4_txq.c
|+++ b/drivers/net/mlx4/mlx4_txq.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk-next-eventdev
29525:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 397.
Hunk #2 succeeded at 6127 with fuzz 2 (offset 5671 lines).
Hunk #3 succeeded at 6293 with fuzz 2 (offset 5761 lines).
1 out of 3 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 93.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
can't find file to patch at input line 52
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_ethdev.c b/drivers/net/mlx4/mlx4_ethdev.c
|index a9e8059..95cc6e4 100644
|--- a/drivers/net/mlx4/mlx4_ethdev.c
|+++ b/drivers/net/mlx4/mlx4_ethdev.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/mlx4/mlx4_prm.h
can't find file to patch at input line 82
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxtx.c b/drivers/net/mlx4/mlx4_rxtx.c
|index 4200716..2757aec 100644
|--- a/drivers/net/mlx4/mlx4_rxtx.c
|+++ b/drivers/net/mlx4/mlx4_rxtx.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 120
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxtx.h b/drivers/net/mlx4/mlx4_rxtx.h
|index 1b90533..dc283e1 100644
|--- a/drivers/net/mlx4/mlx4_rxtx.h
|+++ b/drivers/net/mlx4/mlx4_rxtx.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 133
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_txq.c b/drivers/net/mlx4/mlx4_txq.c
|index 9333311..2d776eb 100644
|--- a/drivers/net/mlx4/mlx4_txq.c
|+++ b/drivers/net/mlx4/mlx4_txq.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
DPDK STV team
reply other threads:[~2017-10-03 11: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='7327ef$47heg2@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=matan@mellanox.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).