From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: zbigniew.bodek@caviumnetworks.com
Subject: [dpdk-test-report] |FAILURE| pw19747 [PATCH v6 5/8] doc: update documentation about ARMv8 crypto PMD
Date: 18 Jan 2017 13:55:18 -0800 [thread overview]
Message-ID: <63cbe6$11713d4@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1597 bytes --]
Test-Label: Intel compilation
Test-Status: FAILURE
http://dpdk.org/patch/19747
_apply patch file failure_
Submitter: zbigniew.bodek@caviumnetworks.com
Date: Wed, 18 Jan 2017 21:01:55 +0100
DPDK git baseline: Repo:dpdk-next-crypto, Branch:master, CommitID:22e382ec8dbb964535bd057f35fd84dc5b761dcb
Repo:dpdk-next-net, Branch:master, CommitID:2d440d30b571cffbb6faa281089c2f39c8c792e1
Apply patch file failed:
Repo: dpdk-next-net
19747:
patching file doc/guides/cryptodevs/armv8.rst
patching file doc/guides/cryptodevs/index.rst
patching file doc/guides/cryptodevs/overview.rst
Hunk #1 FAILED at 33.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/cryptodevs/overview.rst.rej
patching file doc/guides/rel_notes/release_17_02.rst
Hunk #1 succeeded at 178 with fuzz 2 (offset 3 lines).
Repo: dpdk-next-virtio
19747:
patching file doc/guides/cryptodevs/armv8.rst
patching file doc/guides/cryptodevs/index.rst
patching file doc/guides/cryptodevs/overview.rst
Hunk #1 FAILED at 33.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/cryptodevs/overview.rst.rej
patching file doc/guides/rel_notes/release_17_02.rst
Hunk #1 succeeded at 178 with fuzz 2 (offset 3 lines).
Repo: dpdk
19747:
patching file doc/guides/cryptodevs/armv8.rst
patching file doc/guides/cryptodevs/index.rst
patching file doc/guides/cryptodevs/overview.rst
Hunk #1 FAILED at 33.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/cryptodevs/overview.rst.rej
patching file doc/guides/rel_notes/release_17_02.rst
Hunk #1 succeeded at 178 with fuzz 2 (offset 3 lines).
DPDK STV team
reply other threads:[~2017-01-18 21:55 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='63cbe6$11713d4@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=zbigniew.bodek@caviumnetworks.com \
/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).