From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: anatoly.burakov@intel.com
Subject: [dpdk-test-report] |FAILURE| pw35592 [PATCH 12/41] eal: read hugepage counts from node-specific sysfs path
Date: 03 Mar 2018 06:54:50 -0800 [thread overview]
Message-ID: <f7a79a$15553u@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/35592
_apply patch file failure_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Sat, 3 Mar 2018 13:45:56 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:92924b207b124c156f7b6dff75110d6af83d971f
Repo:dpdk-next-crypto, Branch:master, CommitID:92924b207b124c156f7b6dff75110d6af83d971f
Repo:dpdk-next-net, Branch:master, CommitID:01ba67b5f5fbc32e546f3e3aa6672968559b98d8
Repo:dpdk-next-virtio, Branch:master, CommitID:0c111b84bd50bef56333bb21747c8767b86469af
Repo:dpdk, Branch:master, CommitID:c06ddf9698e0c2a9653cfa971f9ddc205065662c
Apply patch file failed:
This patchset 35586-35602 apply failed on all repoes, please check error details at:
http://dpdk.org/patch/35598
http://dpdk.org/patch/35597
http://dpdk.org/patch/35602
http://dpdk.org/patch/35601
http://dpdk.org/patch/35596
DPDK STV team
reply other threads:[~2018-03-03 14:54 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='f7a79a$15553u@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=anatoly.burakov@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).