From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xinfengx.zhao@intel.com, zhaoyan.chen@intel.com, peipeix.lu@intel.com
Subject: [dpdk-test-report] |FAILURE| pw39478[dpdk-dev, 3/3] net/sfc: rely on supported device Rx offload check in ethdev
Date: 08 May 2018 08:13:04 -0700 [thread overview]
Message-ID: <0590c7$1jlioi@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2745 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/39478
_apply issues_
Submitter: Andrew Rybchenko <arybchenko@solarflare.com>
Date: 2018-05-08 15:04:24
DPDK git baseline:
Repo:dpdk-master, CommitID: 5751ff40fed0f7dc359e983d80c768126328561f
Repo:dpdk-next-eventdev, CommitID: fcde84b5f85b3c1a5d5564299fd49c58ca20370d
Repo:dpdk-next-net, CommitID: 9e1d6be043b55ac34a57d4a6ef1c16da84688f40
Repo:dpdk-next-crypto, CommitID: 9e3a32fcd3d10866fcd2519be3d577e557a6719c
Repo:dpdk-next-virtio, CommitID: 037c0996bc927342f157426739e0cb63f2db8689
*Repo: dpdk-master
Checking patch drivers/net/sfc/sfc_rx.c...
error: while searching for:
return caps;
}
static void
sfc_rx_log_offloads(struct sfc_adapter *sa, const char *offload_group,
--
static int
sfc_rx_qcheck_conf(struct sfc_adapter *sa, unsigned int rxq_max_fill_level,
const struct rte_eth_rxconf *rx_conf,
error: patch failed: drivers/net/sfc/sfc_rx.c:814
error: drivers/net/sfc/sfc_rx.c: patch does not apply
*Repo: dpdk-next-eventdev
Checking patch drivers/net/sfc/sfc_rx.c...
error: while searching for:
return caps;
}
static void
sfc_rx_log_offloads(struct sfc_adapter *sa, const char *offload_group,
--
static int
sfc_rx_qcheck_conf(struct sfc_adapter *sa, unsigned int rxq_max_fill_level,
const struct rte_eth_rxconf *rx_conf,
error: patch failed: drivers/net/sfc/sfc_rx.c:814
error: drivers/net/sfc/sfc_rx.c: patch does not apply
*Repo: dpdk-next-net
Checking patch drivers/net/sfc/sfc_rx.c...
error: while searching for:
return caps;
}
static void
sfc_rx_log_offloads(struct sfc_adapter *sa, const char *offload_group,
--
static int
sfc_rx_qcheck_conf(struct sfc_adapter *sa, unsigned int rxq_max_fill_level,
const struct rte_eth_rxconf *rx_conf,
error: patch failed: drivers/net/sfc/sfc_rx.c:814
error: drivers/net/sfc/sfc_rx.c: patch does not apply
*Repo: dpdk-next-crypto
Checking patch drivers/net/sfc/sfc_rx.c...
error: while searching for:
return caps;
}
static void
sfc_rx_log_offloads(struct sfc_adapter *sa, const char *offload_group,
--
static int
sfc_rx_qcheck_conf(struct sfc_adapter *sa, unsigned int rxq_max_fill_level,
const struct rte_eth_rxconf *rx_conf,
error: patch failed: drivers/net/sfc/sfc_rx.c:814
error: drivers/net/sfc/sfc_rx.c: patch does not apply
*Repo: dpdk-next-virtio
Checking patch drivers/net/sfc/sfc_rx.c...
error: while searching for:
return caps;
}
static void
sfc_rx_log_offloads(struct sfc_adapter *sa, const char *offload_group,
--
static int
sfc_rx_qcheck_conf(struct sfc_adapter *sa, unsigned int rxq_max_fill_level,
const struct rte_eth_rxconf *rx_conf,
error: patch failed: drivers/net/sfc/sfc_rx.c:814
error: drivers/net/sfc/sfc_rx.c: patch does not apply
DPDK STV team
next reply other threads:[~2018-05-08 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 15:13 sys_stv [this message]
2018-05-10 8:18 sys_stv
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='0590c7$1jlioi@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=peipeix.lu@intel.com \
--cc=test-report@dpdk.org \
--cc=xinfengx.zhao@intel.com \
--cc=zhaoyan.chen@intel.com \
/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).