From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xinfengx.zhao@intel.com, zhaoyan.chen@intel.com, peipeix.lu@intel.com
Subject: [dpdk-test-report] |FAILURE| pw36343[dpdk-dev, v2, 2/3] bus/pci: expose sysfs parsing API
Date: 10 May 2018 00:58:50 -0700 [thread overview]
Message-ID: <0590c7$1k587u@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3609 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/36343
_apply issues_
Submitter: Xiao Wang <xiao.w.wang@intel.com>
Date: 2018-03-21 13:21:07
DPDK git baseline:
Repo:dpdk-master, CommitID: 8ea41438832a360aed2b7ba49fb75e310a2ff1dc
Repo:dpdk-next-eventdev, CommitID: 640b0d1e510e111694c25145466f37867453837f
Repo:dpdk-next-net, CommitID: 774c1892c434dba09998ccc76b956feb72224571
Repo:dpdk-next-crypto, CommitID: 728ca9b0d5abea82cd01dee6645456a9d56215f7
Repo:dpdk-next-virtio, CommitID: 037c0996bc927342f157426739e0cb63f2db8689
*Repo: dpdk-master
Checking patch drivers/bus/pci/Makefile...
error: while searching for:
CFLAGS += -I$(RTE_SDK)/lib/librte_eal/common
CFLAGS += -I$(RTE_SDK)/lib/librte_eal/$(SYSTEM)app/eal
LDLIBS += -lrte_eal -lrte_mbuf -lrte_mempool -lrte_ring
LDLIBS += -lrte_ethdev -lrte_pci
error: patch failed: drivers/bus/pci/Makefile:49
error: drivers/bus/pci/Makefile: patch does not apply
Checking patch drivers/bus/pci/bsd/pci.c...
Checking patch drivers/bus/pci/linux/pci.c...
Hunk #2 succeeded at 177 (offset 4 lines).
Hunk #3 succeeded at 310 (offset 4 lines).
Hunk #4 succeeded at 318 (offset 4 lines).
*Repo: dpdk-next-eventdev
Checking patch drivers/bus/pci/Makefile...
error: while searching for:
CFLAGS += -I$(RTE_SDK)/lib/librte_eal/common
CFLAGS += -I$(RTE_SDK)/lib/librte_eal/$(SYSTEM)app/eal
LDLIBS += -lrte_eal -lrte_mbuf -lrte_mempool -lrte_ring
LDLIBS += -lrte_ethdev -lrte_pci
error: patch failed: drivers/bus/pci/Makefile:49
error: drivers/bus/pci/Makefile: patch does not apply
Checking patch drivers/bus/pci/bsd/pci.c...
Checking patch drivers/bus/pci/linux/pci.c...
Hunk #2 succeeded at 177 (offset 4 lines).
Hunk #3 succeeded at 310 (offset 4 lines).
Hunk #4 succeeded at 318 (offset 4 lines).
*Repo: dpdk-next-net
Checking patch drivers/bus/pci/Makefile...
error: while searching for:
CFLAGS += -I$(RTE_SDK)/lib/librte_eal/common
CFLAGS += -I$(RTE_SDK)/lib/librte_eal/$(SYSTEM)app/eal
LDLIBS += -lrte_eal -lrte_mbuf -lrte_mempool -lrte_ring
LDLIBS += -lrte_ethdev -lrte_pci
error: patch failed: drivers/bus/pci/Makefile:49
error: drivers/bus/pci/Makefile: patch does not apply
Checking patch drivers/bus/pci/bsd/pci.c...
Checking patch drivers/bus/pci/linux/pci.c...
Hunk #2 succeeded at 177 (offset 4 lines).
Hunk #3 succeeded at 310 (offset 4 lines).
Hunk #4 succeeded at 318 (offset 4 lines).
*Repo: dpdk-next-crypto
Checking patch drivers/bus/pci/Makefile...
error: while searching for:
CFLAGS += -I$(RTE_SDK)/lib/librte_eal/common
CFLAGS += -I$(RTE_SDK)/lib/librte_eal/$(SYSTEM)app/eal
LDLIBS += -lrte_eal -lrte_mbuf -lrte_mempool -lrte_ring
LDLIBS += -lrte_ethdev -lrte_pci
error: patch failed: drivers/bus/pci/Makefile:49
error: drivers/bus/pci/Makefile: patch does not apply
Checking patch drivers/bus/pci/bsd/pci.c...
Checking patch drivers/bus/pci/linux/pci.c...
Hunk #2 succeeded at 177 (offset 4 lines).
Hunk #3 succeeded at 310 (offset 4 lines).
Hunk #4 succeeded at 318 (offset 4 lines).
*Repo: dpdk-next-virtio
Checking patch drivers/bus/pci/Makefile...
error: while searching for:
CFLAGS += -I$(RTE_SDK)/lib/librte_eal/common
CFLAGS += -I$(RTE_SDK)/lib/librte_eal/$(SYSTEM)app/eal
LDLIBS += -lrte_eal -lrte_mbuf -lrte_mempool -lrte_ring
LDLIBS += -lrte_ethdev -lrte_pci
error: patch failed: drivers/bus/pci/Makefile:49
error: drivers/bus/pci/Makefile: patch does not apply
Checking patch drivers/bus/pci/bsd/pci.c...
Checking patch drivers/bus/pci/linux/pci.c...
Hunk #2 succeeded at 177 (offset 4 lines).
Hunk #3 succeeded at 310 (offset 4 lines).
Hunk #4 succeeded at 318 (offset 4 lines).
DPDK STV team
reply other threads:[~2018-05-10 7:58 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='0590c7$1k587u@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=peipeix.lu@intel.com \
--cc=test-report@dpdk.org \
--cc=xinfengx.zhao@intel.com \
--cc=zhaoyan.chen@intel.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).