From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw56163[v4, 8/8] eal: unify internal config initialization
Date: 08 Jul 2019 01:32:32 -0700 [thread overview]
Message-ID: <ee68f5$7d77du@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1589 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/56163
_apply issues_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: 2019-07-05 13:10:34
Reply_mail: 4d42544cf722666e493a236d5a1065c57726e8fa.1562332112.git.anatoly.burakov@intel.com
DPDK git baseline:
Repo:dpdk, CommitID: 7ddd2e81697bfc04eafac35082c4e3271721a780
*Repo: dpdk
void
rte_mcfg_mem_read_lock(void)
{
error: patch failed: lib/librte_eal/common/eal_common_mcfg.c:31
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:
uint8_t dma_maskbits; /**< Keeps the more restricted dma mask. */
};
/* wait until primary process initialization is complete */
void
eal_mcfg_wait_complete(void);
error: patch failed: lib/librte_eal/common/eal_memcfg.h:69
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:
case RTE_PROC_PRIMARY:
if (rte_eal_config_create() < 0)
return -1;
break;
case RTE_PROC_SECONDARY:
if (rte_eal_config_attach() < 0)
error: patch failed: lib/librte_eal/freebsd/eal/eal.c:379
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 ptype;
}
--
/* Sets up rte_config structure with the pointer to shared memory config.*/
static int
rte_config_init(void)
error: patch failed: lib/librte_eal/linux/eal/eal.c:473
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$7d77du@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).