From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw61958[v7, 07/15] sched: update memory compute to support flexiblity
Date: 25 Oct 2019 20:45:14 -0700 [thread overview]
Message-ID: <ee68f5$8dbca1@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/61958
_apply issues_
Submitter: Jasvinder Singh <jasvinder.singh@intel.com>
Date: 2019-10-25 10:51:16
Reply_mail: 20191025105124.6950-8-jasvinder.singh@intel.com
DPDK git baseline:
Repo:dpdk-next-net, CommitID: feb6c19751a15bc13d2289ee143128f14faf7439
Repo:dpdk, CommitID: b50bcefdcc087e3b945c05ddbe8f0dff399ff405
*Repo: dpdk-next-net
static uint32_t
rte_sched_subport_get_array_base(struct rte_sched_subport_params *params,
enum rte_sched_subport_array array)
error: patch failed: lib/librte_sched/rte_sched.c:476
error: lib/librte_sched/rte_sched.c: patch does not apply
Checking patch lib/librte_sched/rte_sched.h...
error: while searching for:
/**
* Hierarchical scheduler memory footprint size per port
--
/*
* Statistics
*
error: patch failed: lib/librte_sched/rte_sched.h:373
error: lib/librte_sched/rte_sched.h: patch does not apply
*Repo: dpdk
static uint32_t
rte_sched_subport_get_array_base(struct rte_sched_subport_params *params,
enum rte_sched_subport_array array)
error: patch failed: lib/librte_sched/rte_sched.c:476
error: lib/librte_sched/rte_sched.c: patch does not apply
Checking patch lib/librte_sched/rte_sched.h...
error: while searching for:
/**
* Hierarchical scheduler memory footprint size per port
--
/*
* Statistics
*
error: patch failed: lib/librte_sched/rte_sched.h:373
error: lib/librte_sched/rte_sched.h: patch does not apply
DPDK STV team
reply other threads:[~2019-10-26 3:45 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$8dbca1@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).