From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: akhil.goyal@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw30410 [PATCH v4 06/12] ethdev: support security APIs
Date: 17 Oct 2017 19:43:28 -0700 [thread overview]
Message-ID: <1a8a4b$13v221r@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/30410
_apply patch file failure_
Submitter: Akhil Goyal <akhil.goyal@nxp.com>
Date: Sun, 15 Oct 2017 03:47:33 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:c4958a2f84f03feb5a0c2b070c925bba68a87164
Repo:dpdk-next-crypto, Branch:master, CommitID:54d551737d99ee39587c4c3881688b4be3bae2cb
Repo:dpdk-next-net, Branch:master, CommitID:6b9ed026a8704b9e5ee5da7997617ef7cc82e114
Repo:dpdk-next-virtio, Branch:master, CommitID:7fbf963714bf7525a28024c5f54bba2b4b3b1a1f
Repo:dpdk, Branch:master, CommitID:6b9ed026a8704b9e5ee5da7997617ef7cc82e114
Apply patch file failed:
Repo: dpdk-next-virtio
30410:
patching file lib/librte_ether/rte_ethdev.c
Hunk #1 succeeded at 303 (offset 2 lines).
patching file lib/librte_ether/rte_ethdev.h
Hunk #2 succeeded at 380 (offset -1 lines).
Hunk #3 succeeded at 709 (offset -1 lines).
Hunk #4 succeeded at 972 (offset -2 lines).
Hunk #5 succeeded at 1002 (offset -2 lines).
Hunk #6 succeeded at 1741 (offset -2 lines).
Hunk #7 succeeded at 1804 (offset -2 lines).
Hunk #8 succeeded at 1816 (offset -2 lines).
patching file lib/librte_ether/rte_ethdev_version.map
Hunk #1 FAILED at 194.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_ether/rte_ethdev_version.map.rej
DPDK STV team
reply other threads:[~2017-10-18 2:43 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='1a8a4b$13v221r@fmsmga001.fm.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).