From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw44998[v5, 3/8] net/mvneta: support for setting of MTU
Date: 20 Sep 2018 20:23:08 -0700 [thread overview]
Message-ID: <0590c7$2o4k7j@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/44998
_apply issues_
Submitter: Andrzej Ostruszka <amo@semihalf.com>
Date: 2018-09-20 09:05:34
DPDK git baseline:
Repo:dpdk-master, CommitID: 55d6bb67c9b3858b50df6c74a3b37d87b271a027
Repo:dpdk-next-eventdev, CommitID: c6aaa1a58c301140fba28b772c48f082e9206c23
Repo:dpdk-next-net, CommitID: 16e6f3573caf11b18bb76aaf758e7e4ad7be5a85
Repo:dpdk-next-crypto, CommitID: 7ee5afa5db967a211cad28e83ab589d188cd3ec4
Repo:dpdk-next-virtio, CommitID: 712d1cfe3b7068746a05b744da6b6861e6940913
*Repo: dpdk-master
Checking patch drivers/net/mvneta/mvneta_ethdev.c...
error: drivers/net/mvneta/mvneta_ethdev.c: No such file or directory
*Repo: dpdk-next-eventdev
Checking patch drivers/net/mvneta/mvneta_ethdev.c...
error: drivers/net/mvneta/mvneta_ethdev.c: No such file or directory
*Repo: dpdk-next-net
Checking patch drivers/net/mvneta/mvneta_ethdev.c...
error: drivers/net/mvneta/mvneta_ethdev.c: No such file or directory
*Repo: dpdk-next-crypto
Checking patch drivers/net/mvneta/mvneta_ethdev.c...
error: drivers/net/mvneta/mvneta_ethdev.c: No such file or directory
*Repo: dpdk-next-virtio
Checking patch drivers/net/mvneta/mvneta_ethdev.c...
error: drivers/net/mvneta/mvneta_ethdev.c: No such file or directory
DPDK STV team
reply other threads:[~2018-09-21 3:23 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$2o4k7j@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).