automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: deepak.k.jain@intel.com, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw15230-15231 crypto/qat: add NULL capability to Intel QAT driver
Date: 18 Aug 2016 23:36:35 -0700	[thread overview]
Message-ID: <8dba68$v3kmf6@fmsmga002.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 764 bytes --]


Test-Label: Intel Niantic on Fedora
Test-Status: ERROR

Patchwork ID: 15230-15231
http://www.dpdk.org/dev/patchwork/patch/15231/
Submitter: Deepak Kumar JAIN <deepak.k.jain@intel.com>
Date: Thu, 18 Aug 2016 14:34:31 +0100
DPDK git baseline: 0b50aa7c079ccefaef70b8e406c4e7a09eddfa63

Check patch:Success

patch file error:
15230: 
patching file doc/guides/cryptodevs/qat.rst Hunk #2 FAILED at 61.
1 out of 2 hunks FAILED -- saving rejects to file doc/guides/cryptodevs/qat.rst.rej patching file drivers/crypto/qat/qat_adf/qat_algs_build_desc.c
Hunk #1 succeeded at 715 with fuzz 2 (offset -5 lines).
patching file drivers/crypto/qat/qat_crypto.c Hunk #1 succeeded at 406 (offset -21 lines).
Hunk #2 succeeded at 530 with fuzz 1 (offset -30 lines).

DPDK STV team 

                 reply	other threads:[~2016-08-19  6:36 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$v3kmf6@fmsmga002.fm.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).