From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: keith.wiles@intel.com
Subject: [dpdk-test-report] |FAILURE| pw20204 [PATCH v3 6/7] net/tap: link set down must be done before close
Date: 06 Feb 2017 15:03:24 -0800 [thread overview]
Message-ID: <e81775$10snq57@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1667 bytes --]
Test-Label: Intel compilation
Test-Status: FAILURE
http://dpdk.org/patch/20204
_apply patch file failure_
Submitter: Keith Wiles <keith.wiles@intel.com>
Date: Mon, 6 Feb 2017 13:40:37 -0600
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:f13b12ef54e21fe166ea5fc256d80becf3f8b2db
Repo:dpdk-next-crypto, Branch:master, CommitID:5b243cbab26652027c3848e35fe595025f3622ea
Repo:dpdk-next-net, Branch:master, CommitID:193b5df8011470892fd9f6c93081c5d5986be188
Repo:dpdk-next-virtio, Branch:master, CommitID:a69de21ee881adb095667a15a28fbf5044e22a28
Repo:dpdk, Branch:master, CommitID:5b243cbab26652027c3848e35fe595025f3622ea
Apply patch file failed:
Repo: dpdk
20204:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 353.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
Repo: dpdk-next-crypto
20204:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 353.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
Repo: dpdk-next-net
20204:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 353.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
Repo: dpdk-next-virtio
20204:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 353.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
Repo: dpdk-next-eventdev
20204:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 FAILED at 353.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
DPDK STV team
reply other threads:[~2017-02-06 23:03 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='e81775$10snq57@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=keith.wiles@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).