From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: erik.g.carrillo@intel.com
Subject: [dpdk-test-report] |FAILURE| pw37204 [PATCH v11 3/9] eventtimer: add common code
Date: 16 Apr 2018 11:57:29 -0700 [thread overview]
Message-ID: <a7de25$142bvi@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1551 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/37204
_apply patch file failure_
Submitter: Erik Carrillo <erik.g.carrillo@intel.com>
Date: Wed, 4 Apr 2018 16:51:07 -0500
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fe5abd3150bc1caa8369e743c395c39f53265597
Repo:dpdk-next-crypto, Branch:master, CommitID:25b13dcbd5a779548d1a67f60684cabf532a17f8
Repo:dpdk-next-net, Branch:master, CommitID:60c2e4012a2c2f87f1868b95f4efb60d1a8e2adf
Repo:dpdk-next-virtio, Branch:master, CommitID:8adbe7e4847060d091c46abcbecd3dfea8362b7a
Repo:dpdk, Branch:master, CommitID:6e8a721044c6ef677e67991f3f2a9bd0870eecc2
Apply patch file failed:
Repo: dpdk-next-virtio
37204:
patching file config/common_base
Hunk #1 succeeded at 563 (offset 13 lines).
patching file drivers/event/sw/sw_evdev.c
patching file lib/librte_eventdev/Makefile
patching file lib/librte_eventdev/rte_event_timer_adapter.c
patching file lib/librte_eventdev/rte_event_timer_adapter_pmd.h
patching file lib/librte_eventdev/rte_eventdev.c
patching file lib/librte_eventdev/rte_eventdev.h
Hunk #1 succeeded at 215 with fuzz 1.
Hunk #2 succeeded at 1070 (offset -46 lines).
patching file lib/librte_eventdev/rte_eventdev_pmd.h
Hunk #3 succeeded at 672 with fuzz 1.
patching file lib/librte_eventdev/rte_eventdev_version.map
Hunk #2 FAILED at 79.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eventdev/rte_eventdev_version.map.rej
DPDK STV team
reply other threads:[~2018-04-16 18:57 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='a7de25$142bvi@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=erik.g.carrillo@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).