From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw65172[v6, 04/11] examples/l3fwd: add ethdev setup based on eventdev
Date: 13 Feb 2020 10:39:56 -0800 [thread overview]
Message-ID: <ee68f5$9b8rpq@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1463 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/65172
_apply issues_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: 2020-01-28 05:34:58
Reply_mail: 20200128053506.2173-5-pbhagavatula@marvell.com
DPDK git baseline:
Repo:dpdk, CommitID: 2a115479c6361f9667efaa30ceb0dbdcbd931f48
*Repo: dpdk
#define MAX_RX_QUEUE_PER_LCORE 16
/*
error: patch failed: examples/l3fwd/l3fwd.h:16
error: examples/l3fwd/l3fwd.h: patch does not apply
Checking patch examples/l3fwd/l3fwd_event.c...
error: while searching for:
#include "l3fwd.h"
#include "l3fwd_event.h"
struct l3fwd_event_resources *
l3fwd_get_eventdev_rsrc(void)
{
error: patch failed: examples/l3fwd/l3fwd_event.c:10
error: examples/l3fwd/l3fwd_event.c: patch does not apply
Checking patch examples/l3fwd/l3fwd_event.h...
error: while searching for:
};
--
void l3fwd_event_resource_setup(void);
void l3fwd_event_set_generic_ops(struct l3fwd_event_setup_ops *ops);
void l3fwd_event_set_internal_port_ops(struct l3fwd_event_setup_ops *ops);
error: patch failed: examples/l3fwd/l3fwd_event.h:72
error: examples/l3fwd/l3fwd_event.h: patch does not apply
Checking patch examples/l3fwd/main.c...
error: while searching for:
#include "l3fwd.h"
#include "l3fwd_event.h"
--
#define MAX_TX_QUEUE_PER_PORT RTE_MAX_ETHPORTS
#define MAX_RX_QUEUE_PER_PORT 128
error: patch failed: examples/l3fwd/main.c:48
error: examples/l3fwd/main.c: patch does not apply
DPDK STV team
reply other threads:[~2020-02-13 18:39 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$9b8rpq@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).