From: sys_stv@intel.com
To: deepak.k.jain@intel.com, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw15320-15323 crypto/qat: enable Kasumi F9 support in QAT driver
Date: 25 Aug 2016 22:32:07 -0700 [thread overview]
Message-ID: <1f969b$ud9g0g@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2389 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 15320-15323
http://www.dpdk.org/dev/patchwork/patch/15323/
Submitter: Deepak Kumar JAIN <deepak.k.jain@intel.com>
Date: Thu, 25 Aug 2016 14:23:36 +0100
DPDK git baseline: e22856313fff2db12d8e132dad446bbf74cf29a5
Check patch:Success
patch file error:
15320:
patching file doc/guides/cryptodevs/qat.rst Hunk #1 FAILED at 63.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/cryptodevs/qat.rst.rej patching file drivers/crypto/qat/qat_adf/qat_algs.h
patching file drivers/crypto/qat/qat_adf/qat_algs_build_desc.c
Hunk #1 succeeded at 86 with fuzz 2 (offset -10 lines).
Hunk #2 FAILED at 562.
Hunk #3 FAILED at 608.
Hunk #4 FAILED at 725.
3 out of 4 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 succeeded at 283 (offset -21 lines).
Hunk #2 FAILED at 582.
Hunk #3 succeeded at 559 with fuzz 1 (offset -31 lines).
Hunk #4 succeeded at 804 with fuzz 2 (offset -32 lines).
1 out of 4 hunks FAILED -- saving rejects to file drivers/crypto/qat/qat_crypto.c.rej
15321:
patching file app/test/test_cryptodev.c
Hunk #1 succeeded at 1966 (offset -1 lines).
Hunk #2 succeeded at 4160 with fuzz 2 (offset 8 lines).
Hunk #3 FAILED at 4257.
1 out of 3 hunks FAILED -- saving rejects to file app/test/test_cryptodev.c.rej patching file app/test/test_cryptodev_kasumi_hash_test_vectors.h
15322:
patching file doc/guides/cryptodevs/qat.rst Hunk #1 FAILED at 51.
Hunk #2 FAILED at 70.
2 out of 2 hunks FAILED -- saving rejects to file doc/guides/cryptodevs/qat.rst.rej patching file drivers/crypto/qat/qat_adf/qat_algs.h
Hunk #1 FAILED at 57.
Hunk #2 succeeded at 127 (offset -10 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/crypto/qat/qat_adf/qat_algs.h.rej
patching file drivers/crypto/qat/qat_adf/qat_algs_build_desc.c
Hunk #1 FAILED at 457.
Hunk #2 FAILED at 507.
Hunk #3 FAILED at 524.
Hunk #4 succeeded at 836 (offset -23 lines).
3 out of 4 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 succeeded at 283 (offset -41 lines).
Hunk #2 FAILED at 474.
Hunk #3 succeeded at 767 (offset -54 lines).
1 out of 3 hunks FAILED -- saving rejects to file drivers/crypto/qat/qat_crypto.c.rej
DPDK STV team
reply other threads:[~2016-08-26 5:32 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='1f969b$ud9g0g@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=deepak.k.jain@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).