From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: akhil.goyal@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw32223 [PATCH 1/5] crypto/dpaa_sec: optimize virt to phy conversion
Date: 25 Dec 2017 06:23:05 -0800 [thread overview]
Message-ID: <1f4ae4$k7g40@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/32223
_apply patch file failure_
Submitter: Akhil Goyal <akhil.goyal@nxp.com>
Date: Wed, 13 Dec 2017 19:26:55 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:36d020c107ba65a584784a3f52484ea1698d4f9d
Repo:dpdk-next-crypto, Branch:master, CommitID:b8cde08731e9f6a7b250a7c5b10212bf009659a4
Repo:dpdk-next-net, Branch:master, CommitID:929a80374047dacd785c42db8e240901af041e9a
Repo:dpdk-next-virtio, Branch:master, CommitID:4f761c94b520ce71c56be1c913e54a4179b81c43
Repo:dpdk, Branch:master, CommitID:91a0eabf00cbd78a8630ff1b9279af1b2db92122
Apply patch file failed:
Repo: dpdk-next-virtio
32223:
patching file drivers/crypto/dpaa_sec/dpaa_sec.c
Hunk #2 succeeded at 132 with fuzz 2.
Hunk #4 succeeded at 613 (offset 1 line).
Hunk #5 succeeded at 662 (offset -4 lines).
Hunk #6 succeeded at 704 (offset -8 lines).
Hunk #7 succeeded at 750 with fuzz 1 (offset -7 lines).
Hunk #8 succeeded at 764 with fuzz 2 (offset -7 lines).
Hunk #9 succeeded at 813 (offset -10 lines).
Hunk #10 succeeded at 844 with fuzz 1 (offset -9 lines).
Hunk #11 FAILED at 867.
1 out of 11 hunks FAILED -- saving rejects to file drivers/crypto/dpaa_sec/dpaa_sec.c.rej
patching file drivers/crypto/dpaa_sec/dpaa_sec.h
DPDK STV team
reply other threads:[~2017-12-25 14:23 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='1f4ae4$k7g40@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=akhil.goyal@nxp.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).