From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw41311[v2] net/e1000: add support for check descriptor status APIs
Date: 20 Jun 2018 02:20:59 -0700 [thread overview]
Message-ID: <0590c7$1v22qf@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3516 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/41311
_apply issues_
Submitter: Wei Zhao <wei.zhao1@intel.com>
Date: 2018-06-20 08:52:53
DPDK git baseline:
Repo:dpdk-master, CommitID: 9d7ee7fc689cabc085106579c2842cf2231e360a
Repo:dpdk-next-eventdev, CommitID: fb7271e596b4b363e53ca0926a709fe1725912cd
Repo:dpdk-next-net, CommitID: 9d7ee7fc689cabc085106579c2842cf2231e360a
Repo:dpdk-next-crypto, CommitID: 937dac86c6212cc76850a3629a8d451feb625e85
Repo:dpdk-next-virtio, CommitID: 450a4d24cdc9b99e8299876fe380363282f67539
*Repo: dpdk-master
Checking patch doc/guides/rel_notes/release_18_08.rst...
error: while searching for:
Also, make sure to start the actual text at the margin.
=========================================================
* **Added fm10k ethernet driver to support check descriptor status APIs.**
Fm10k nic need to support check descriptor status APIs, they are
rte_eth_rx_descriptor_status and rte_eth_tx_descriptor_status.
add ops pointer with new function which enable feature.
error: patch failed: doc/guides/rel_notes/release_18_08.rst:41
error: doc/guides/rel_notes/release_18_08.rst: patch does not apply
Checking patch drivers/net/e1000/igb_ethdev.c...
*Repo: dpdk-next-eventdev
Checking patch doc/guides/rel_notes/release_18_08.rst...
error: doc/guides/rel_notes/release_18_08.rst: No such file or directory
Checking patch drivers/net/e1000/igb_ethdev.c...
*Repo: dpdk-next-net
Checking patch doc/guides/rel_notes/release_18_08.rst...
error: while searching for:
Also, make sure to start the actual text at the margin.
=========================================================
* **Added fm10k ethernet driver to support check descriptor status APIs.**
Fm10k nic need to support check descriptor status APIs, they are
rte_eth_rx_descriptor_status and rte_eth_tx_descriptor_status.
add ops pointer with new function which enable feature.
error: patch failed: doc/guides/rel_notes/release_18_08.rst:41
error: doc/guides/rel_notes/release_18_08.rst: patch does not apply
Checking patch drivers/net/e1000/igb_ethdev.c...
*Repo: dpdk-next-crypto
Checking patch doc/guides/rel_notes/release_18_08.rst...
error: while searching for:
Also, make sure to start the actual text at the margin.
=========================================================
* **Added fm10k ethernet driver to support check descriptor status APIs.**
Fm10k nic need to support check descriptor status APIs, they are
rte_eth_rx_descriptor_status and rte_eth_tx_descriptor_status.
add ops pointer with new function which enable feature.
error: patch failed: doc/guides/rel_notes/release_18_08.rst:41
error: doc/guides/rel_notes/release_18_08.rst: patch does not apply
Checking patch drivers/net/e1000/igb_ethdev.c...
*Repo: dpdk-next-virtio
Checking patch doc/guides/rel_notes/release_18_08.rst...
error: while searching for:
Also, make sure to start the actual text at the margin.
=========================================================
* **Added fm10k ethernet driver to support check descriptor status APIs.**
Fm10k nic need to support check descriptor status APIs, they are
rte_eth_rx_descriptor_status and rte_eth_tx_descriptor_status.
add ops pointer with new function which enable feature.
error: patch failed: doc/guides/rel_notes/release_18_08.rst:41
error: doc/guides/rel_notes/release_18_08.rst: patch does not apply
Checking patch drivers/net/e1000/igb_ethdev.c...
DPDK STV team
reply other threads:[~2018-06-20 9:21 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='0590c7$1v22qf@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).