From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: fiona.trahe@intel.com
Subject: [dpdk-test-report] |FAILURE| pw39856 [PATCH 1/5] crypto/qat: cleanup unused and useless trace
Date: 14 May 2018 01:41:27 -0700 [thread overview]
Message-ID: <a7de25$1br0bo@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 8211 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/39856
_apply patch file failure_
Submitter: Fiona Trahe <fiona.trahe@intel.com>
Date: Fri, 11 May 2018 12:31:45 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:3c955492b601d65402c02ac81dfdc7eeb62f23c9
Repo:dpdk-next-crypto, Branch:master, CommitID:e0d88a394e91f446234aa04d0f9e01c150b0d347
Repo:dpdk-next-net, Branch:master, CommitID:dc33238da4be9cf69e44049cd44950fb4fe74e3b
Repo:dpdk-next-virtio, Branch:master, CommitID:037c0996bc927342f157426739e0cb63f2db8689
Repo:dpdk, Branch:master, CommitID:3b97888ab2a8405bcbe198abdcc8ac98ee0f0e96
Apply patch file failed:
Repo: dpdk
39856:
patching file config/common_base
Hunk #1 succeeded at 487 (offset 5 lines).
patching file drivers/crypto/qat/qat_logs.h
patching file drivers/crypto/qat/qat_qp.c
Hunk #1 succeeded at 55 (offset -65 lines).
Hunk #2 FAILED at 193.
Hunk #3 succeeded at 215 with fuzz 1 (offset -45 lines).
Hunk #4 succeeded at 379 (offset -37 lines).
Hunk #5 succeeded at 389 (offset -37 lines).
Hunk #6 FAILED at 444.
Hunk #7 FAILED at 461.
Hunk #8 succeeded at 430 (offset -45 lines).
3 out of 8 hunks FAILED -- saving rejects to file drivers/crypto/qat/qat_qp.c.rej
can't find file to patch at input line 130
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_pmd.c b/drivers/crypto/qat/qat_sym_pmd.c
|index c94a8a1..8797c0e 100644
|--- a/drivers/crypto/qat/qat_sym_pmd.c
|+++ b/drivers/crypto/qat/qat_sym_pmd.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 171
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_session.c b/drivers/crypto/qat/qat_sym_session.c
|index 689596d..83d0fb1 100644
|--- a/drivers/crypto/qat/qat_sym_session.c
|+++ b/drivers/crypto/qat/qat_sym_session.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
7 out of 7 hunks ignored
Repo: dpdk-next-crypto
39856:
patching file config/common_base
patching file drivers/crypto/qat/qat_logs.h
patching file drivers/crypto/qat/qat_qp.c
Hunk #1 succeeded at 55 (offset -65 lines).
Hunk #2 FAILED at 193.
Hunk #3 succeeded at 215 with fuzz 1 (offset -45 lines).
Hunk #4 succeeded at 379 (offset -37 lines).
Hunk #5 succeeded at 389 (offset -37 lines).
Hunk #6 FAILED at 444.
Hunk #7 FAILED at 461.
Hunk #8 succeeded at 430 (offset -45 lines).
3 out of 8 hunks FAILED -- saving rejects to file drivers/crypto/qat/qat_qp.c.rej
can't find file to patch at input line 130
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_pmd.c b/drivers/crypto/qat/qat_sym_pmd.c
|index c94a8a1..8797c0e 100644
|--- a/drivers/crypto/qat/qat_sym_pmd.c
|+++ b/drivers/crypto/qat/qat_sym_pmd.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 171
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_session.c b/drivers/crypto/qat/qat_sym_session.c
|index 689596d..83d0fb1 100644
|--- a/drivers/crypto/qat/qat_sym_session.c
|+++ b/drivers/crypto/qat/qat_sym_session.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
7 out of 7 hunks ignored
Repo: dpdk-next-net
39856:
patching file config/common_base
Hunk #1 succeeded at 485 (offset 3 lines).
patching file drivers/crypto/qat/qat_logs.h
patching file drivers/crypto/qat/qat_qp.c
Hunk #1 succeeded at 55 (offset -65 lines).
Hunk #2 FAILED at 193.
Hunk #3 succeeded at 215 with fuzz 1 (offset -45 lines).
Hunk #4 succeeded at 379 (offset -37 lines).
Hunk #5 succeeded at 389 (offset -37 lines).
Hunk #6 FAILED at 444.
Hunk #7 FAILED at 461.
Hunk #8 succeeded at 430 (offset -45 lines).
3 out of 8 hunks FAILED -- saving rejects to file drivers/crypto/qat/qat_qp.c.rej
can't find file to patch at input line 130
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_pmd.c b/drivers/crypto/qat/qat_sym_pmd.c
|index c94a8a1..8797c0e 100644
|--- a/drivers/crypto/qat/qat_sym_pmd.c
|+++ b/drivers/crypto/qat/qat_sym_pmd.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 171
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_session.c b/drivers/crypto/qat/qat_sym_session.c
|index 689596d..83d0fb1 100644
|--- a/drivers/crypto/qat/qat_sym_session.c
|+++ b/drivers/crypto/qat/qat_sym_session.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
7 out of 7 hunks ignored
Repo: dpdk-next-virtio
39856:
patching file config/common_base
Hunk #1 succeeded at 481 (offset -1 lines).
patching file drivers/crypto/qat/qat_logs.h
patching file drivers/crypto/qat/qat_qp.c
Hunk #1 succeeded at 55 (offset -65 lines).
Hunk #2 FAILED at 193.
Hunk #3 succeeded at 215 with fuzz 1 (offset -45 lines).
Hunk #4 succeeded at 379 (offset -37 lines).
Hunk #5 succeeded at 389 (offset -37 lines).
Hunk #6 FAILED at 444.
Hunk #7 FAILED at 461.
Hunk #8 succeeded at 430 (offset -45 lines).
3 out of 8 hunks FAILED -- saving rejects to file drivers/crypto/qat/qat_qp.c.rej
can't find file to patch at input line 130
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_pmd.c b/drivers/crypto/qat/qat_sym_pmd.c
|index c94a8a1..8797c0e 100644
|--- a/drivers/crypto/qat/qat_sym_pmd.c
|+++ b/drivers/crypto/qat/qat_sym_pmd.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 171
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_session.c b/drivers/crypto/qat/qat_sym_session.c
|index 689596d..83d0fb1 100644
|--- a/drivers/crypto/qat/qat_sym_session.c
|+++ b/drivers/crypto/qat/qat_sym_session.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
7 out of 7 hunks ignored
Repo: dpdk-next-eventdev
39856:
patching file config/common_base
Hunk #1 succeeded at 481 (offset -1 lines).
patching file drivers/crypto/qat/qat_logs.h
patching file drivers/crypto/qat/qat_qp.c
Hunk #1 succeeded at 55 (offset -65 lines).
Hunk #2 FAILED at 193.
Hunk #3 succeeded at 215 with fuzz 1 (offset -45 lines).
Hunk #4 succeeded at 379 (offset -37 lines).
Hunk #5 succeeded at 389 (offset -37 lines).
Hunk #6 FAILED at 444.
Hunk #7 FAILED at 461.
Hunk #8 succeeded at 430 (offset -45 lines).
3 out of 8 hunks FAILED -- saving rejects to file drivers/crypto/qat/qat_qp.c.rej
can't find file to patch at input line 130
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_pmd.c b/drivers/crypto/qat/qat_sym_pmd.c
|index c94a8a1..8797c0e 100644
|--- a/drivers/crypto/qat/qat_sym_pmd.c
|+++ b/drivers/crypto/qat/qat_sym_pmd.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 171
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_session.c b/drivers/crypto/qat/qat_sym_session.c
|index 689596d..83d0fb1 100644
|--- a/drivers/crypto/qat/qat_sym_session.c
|+++ b/drivers/crypto/qat/qat_sym_session.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
7 out of 7 hunks ignored
DPDK STV team
reply other threads:[~2018-05-14 8:41 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='a7de25$1br0bo@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=fiona.trahe@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).