From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw56162[v4, 7/8] eal: unify and move mcfg complete function
Date: 08 Jul 2019 01:32:30 -0700 [thread overview]
Message-ID: <ee68f5$7d77dk@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/56162
_apply issues_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: 2019-07-05 13:10:33
Reply_mail: f898428ab3b0fde2213429a8de1e184521f8ad79.1562332112.git.anatoly.burakov@intel.com
DPDK git baseline:
Repo:dpdk, CommitID: 7ddd2e81697bfc04eafac35082c4e3271721a780
*Repo: dpdk
void
eal_mcfg_wait_complete(void)
{
error: patch failed: lib/librte_eal/common/eal_common_mcfg.c:5
error: lib/librte_eal/common/eal_common_mcfg.c: patch does not apply
Checking patch lib/librte_eal/common/eal_memcfg.h...
error: while searching for:
void
eal_mcfg_wait_complete(void);
#endif /* EAL_MEMCFG_H */
error: patch failed: lib/librte_eal/common/eal_memcfg.h:73
error: lib/librte_eal/common/eal_memcfg.h: patch does not apply
Checking patch lib/librte_eal/freebsd/eal/eal.c...
error: while searching for:
return 0;
}
--
/* return non-zero if hugepages are enabled. */
int rte_eal_has_hugepages(void)
{
error: patch failed: lib/librte_eal/freebsd/eal/eal.c:632
error: lib/librte_eal/freebsd/eal/eal.c: patch does not apply
Checking patch lib/librte_eal/linux/eal/eal.c...
error: while searching for:
return 0;
}
--
/*
* Request iopl privilege for all RPL, returns 0 on success
* iopl() call is mostly for the i386 architecture. For other architectures,
error: patch failed: lib/librte_eal/linux/eal/eal.c:934
error: lib/librte_eal/linux/eal/eal.c: patch does not apply
DPDK STV team
reply other threads:[~2019-07-08 8:32 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='ee68f5$7d77dk@orsmga001.jf.intel.com' \
--to=sys_stv@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).