From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: hejianet@gmail.com
Subject: [dpdk-test-report] |FAILURE| pw31317 [PATCH v6 3/3] ring: introduce new header file to support C11 memory model
Date: 09 Nov 2017 21:59:05 -0800 [thread overview]
Message-ID: <b81db2$5p2l9@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2289 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/31317
_apply patch file failure_
Submitter: Jia He <hejianet@gmail.com>
Date: Fri, 10 Nov 2017 05:23:10 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:b96273bb75fbd99a9732aa4d49658a3525b225b0
Repo:dpdk-next-crypto, Branch:master, CommitID:c05cb4f939082fd7b4892c03372d27e870a0f426
Repo:dpdk-next-net, Branch:master, CommitID:78214fb8821fab0669c1c48f00fc4773e5a9eb98
Repo:dpdk-next-virtio, Branch:master, CommitID:4f761c94b520ce71c56be1c913e54a4179b81c43
Repo:dpdk, Branch:master, CommitID:78214fb8821fab0669c1c48f00fc4773e5a9eb98
Apply patch file failed:
Repo: dpdk
31317:
patching file config/common_armv8a_linuxapp
patching file lib/librte_ring/Makefile
patching file lib/librte_ring/rte_ring.h
Hunk #1 FAILED at 356.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
patching file lib/librte_ring/rte_ring_c11_mem.h
Repo: dpdk-next-crypto
31317:
patching file config/common_armv8a_linuxapp
patching file lib/librte_ring/Makefile
patching file lib/librte_ring/rte_ring.h
Hunk #1 FAILED at 356.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
patching file lib/librte_ring/rte_ring_c11_mem.h
Repo: dpdk-next-net
31317:
patching file config/common_armv8a_linuxapp
patching file lib/librte_ring/Makefile
patching file lib/librte_ring/rte_ring.h
Hunk #1 FAILED at 356.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
patching file lib/librte_ring/rte_ring_c11_mem.h
Repo: dpdk-next-virtio
31317:
patching file config/common_armv8a_linuxapp
patching file lib/librte_ring/Makefile
patching file lib/librte_ring/rte_ring.h
Hunk #1 FAILED at 356.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
patching file lib/librte_ring/rte_ring_c11_mem.h
Repo: dpdk-next-eventdev
31317:
patching file config/common_armv8a_linuxapp
patching file lib/librte_ring/Makefile
patching file lib/librte_ring/rte_ring.h
Hunk #1 FAILED at 356.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_ring/rte_ring.h.rej
patching file lib/librte_ring/rte_ring_c11_mem.h
DPDK STV team
reply other threads:[~2017-11-10 5:59 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='b81db2$5p2l9@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=hejianet@gmail.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).