From: sys_stv@intel.com
To: fiona.trahe@intel.com, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw15330-15335 crypto/qat: code cleanup
Date: 25 Aug 2016 23:12:57 -0700 [thread overview]
Message-ID: <8dba68$v6vhgc@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 960 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 15330,15335
http://www.dpdk.org/dev/patchwork/patch/15330/
Submitter: Fiona Trahe <fiona.trahe@intel.com (fiona.trahe@intel.com)>
Date: Thu, 25 Aug 2016 18:46:59 +0100
DPDK git baseline: e22856313fff2db12d8e132dad446bbf74cf29a5
Check patch:Success
patch file error:
15330:
patching file drivers/crypto/qat/qat_adf/icp_qat_hw.h
patching file drivers/crypto/qat/qat_adf/qat_algs.h
Hunk #1 succeeded at 90 with fuzz 2 (offset -10 lines).
patching file drivers/crypto/qat/qat_adf/qat_algs_build_desc.c
Hunk #1 FAILED at 526.
Hunk #2 FAILED at 535.
Hunk #3 FAILED at 546.
Hunk #4 FAILED at 728.
Hunk #5 FAILED at 804.
5 out of 5 hunks FAILED -- saving rejects to file drivers/crypto/qat/qat_adf/qat_algs_build_desc.c.rej
patching file drivers/crypto/qat/qat_crypto.c Hunk #1 FAILED at 486.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/qat/qat_crypto.c.rej
DPDK STV team
reply other threads:[~2016-08-26 6:12 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='8dba68$v6vhgc@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).