From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw51180[v2] bonding: change mac_addr filled position
Date: 14 Mar 2019 09:14:57 -0700 [thread overview]
Message-ID: <e75792$6c873p@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3568 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/51180
_apply issues_
Submitter: Liang Zhang <zhangliang@bigo.sg>
Date: 2019-03-14 12:27:21
Reply_mail: 1552566441-14658-1-git-send-email-zhangliang@bigo.sg
DPDK git baseline:
Repo:dpdk-master, CommitID: 239912fa798e6e671072ca7ff987afd74c1e506c
Repo:dpdk-next-eventdev, CommitID: e33c3434ebb7f8b19c267d1d2f5f0bb99e93442e
Repo:dpdk-next-net, CommitID: 255a598d3d683d8d68f4a57db886831516249fd3
Repo:dpdk-next-crypto, CommitID: 610e235a11e49a1e5d55c2804a5bc628e87417f1
Repo:dpdk-next-virtio, CommitID: 4f102e62abeb2af8be8d42c71f87b5d33f0dda38
*Repo: dpdk-master
Checking patch drivers/net/bonding/rte_eth_bond_8023ad.c...
error: while searching for:
RTE_ASSERT(lacp->lacpdu.subtype == SLOW_SUBTYPE_LACP);
partner = &lacp->lacpdu.partner;
if (is_same_ether_addr(&partner->port_params.system, &internals->mode4.mac_addr)) {
/* This is LACP frame to the bonding port so pass it to rx_machine */
rx_machine(internals, slave_id, &lacp->lacpdu);
}
rte_pktmbuf_free(lacp_pkt);
error: patch failed: drivers/net/bonding/rte_eth_bond_8023ad.c:791
error: drivers/net/bonding/rte_eth_bond_8023ad.c: patch does not apply
*Repo: dpdk-next-eventdev
Checking patch drivers/net/bonding/rte_eth_bond_8023ad.c...
error: while searching for:
RTE_ASSERT(lacp->lacpdu.subtype == SLOW_SUBTYPE_LACP);
partner = &lacp->lacpdu.partner;
if (is_same_ether_addr(&partner->port_params.system, &internals->mode4.mac_addr)) {
/* This is LACP frame to the bonding port so pass it to rx_machine */
rx_machine(internals, slave_id, &lacp->lacpdu);
}
rte_pktmbuf_free(lacp_pkt);
error: patch failed: drivers/net/bonding/rte_eth_bond_8023ad.c:791
error: drivers/net/bonding/rte_eth_bond_8023ad.c: patch does not apply
*Repo: dpdk-next-net
Checking patch drivers/net/bonding/rte_eth_bond_8023ad.c...
error: while searching for:
RTE_ASSERT(lacp->lacpdu.subtype == SLOW_SUBTYPE_LACP);
partner = &lacp->lacpdu.partner;
if (is_same_ether_addr(&partner->port_params.system, &internals->mode4.mac_addr)) {
/* This is LACP frame to the bonding port so pass it to rx_machine */
rx_machine(internals, slave_id, &lacp->lacpdu);
}
rte_pktmbuf_free(lacp_pkt);
error: patch failed: drivers/net/bonding/rte_eth_bond_8023ad.c:791
error: drivers/net/bonding/rte_eth_bond_8023ad.c: patch does not apply
*Repo: dpdk-next-crypto
Checking patch drivers/net/bonding/rte_eth_bond_8023ad.c...
error: while searching for:
RTE_ASSERT(lacp->lacpdu.subtype == SLOW_SUBTYPE_LACP);
partner = &lacp->lacpdu.partner;
if (is_same_ether_addr(&partner->port_params.system, &internals->mode4.mac_addr)) {
/* This is LACP frame to the bonding port so pass it to rx_machine */
rx_machine(internals, slave_id, &lacp->lacpdu);
}
rte_pktmbuf_free(lacp_pkt);
error: patch failed: drivers/net/bonding/rte_eth_bond_8023ad.c:791
error: drivers/net/bonding/rte_eth_bond_8023ad.c: patch does not apply
*Repo: dpdk-next-virtio
Checking patch drivers/net/bonding/rte_eth_bond_8023ad.c...
error: while searching for:
RTE_ASSERT(lacp->lacpdu.subtype == SLOW_SUBTYPE_LACP);
partner = &lacp->lacpdu.partner;
if (is_same_ether_addr(&partner->port_params.system, &internals->mode4.mac_addr)) {
/* This is LACP frame to the bonding port so pass it to rx_machine */
rx_machine(internals, slave_id, &lacp->lacpdu);
}
rte_pktmbuf_free(lacp_pkt);
error: patch failed: drivers/net/bonding/rte_eth_bond_8023ad.c:791
error: drivers/net/bonding/rte_eth_bond_8023ad.c: patch does not apply
DPDK STV team
reply other threads:[~2019-03-14 16:15 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='e75792$6c873p@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).