From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: ferruh.yigit@intel.com
Subject: [dpdk-test-report] |FAILURE| pw38838 [PATCH v3] net/tap: remove queue specific offload support
Date: 07 May 2018 08:08:40 -0700 [thread overview]
Message-ID: <0590c7$1jbmep@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2589 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38838
_apply patch file failure_
Submitter: Ferruh Yigit <ferruh.yigit@intel.com>
Date: Tue, 24 Apr 2018 18:54:08 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fcde84b5f85b3c1a5d5564299fd49c58ca20370d
Repo:dpdk-next-crypto, Branch:master, CommitID:ee73f98ef481f61eab2f7289f033c6f9113eee8a
Repo:dpdk-next-net, Branch:master, CommitID:29f4ab844cdb61d7241f7241fe860779516b9012
Repo:dpdk-next-virtio, Branch:master, CommitID:037c0996bc927342f157426739e0cb63f2db8689
Repo:dpdk, Branch:master, CommitID:ee73f98ef481f61eab2f7289f033c6f9113eee8a
Apply patch file failed:
Repo: dpdk
38838:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 succeeded at 270 with fuzz 1 (offset -8 lines).
Hunk #2 succeeded at 374 with fuzz 1 (offset -12 lines).
Hunk #3 succeeded at 702 (offset -11 lines).
Hunk #4 FAILED at 1042.
Hunk #5 FAILED at 1123.
2 out of 5 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
Repo: dpdk-next-crypto
38838:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 succeeded at 270 with fuzz 1 (offset -8 lines).
Hunk #2 succeeded at 374 with fuzz 1 (offset -12 lines).
Hunk #3 succeeded at 702 (offset -11 lines).
Hunk #4 FAILED at 1042.
Hunk #5 FAILED at 1123.
2 out of 5 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
Repo: dpdk-next-net
38838:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 succeeded at 270 with fuzz 1 (offset -8 lines).
Hunk #2 succeeded at 374 with fuzz 1 (offset -12 lines).
Hunk #3 succeeded at 702 (offset -11 lines).
Hunk #4 FAILED at 1042.
Hunk #5 FAILED at 1123.
2 out of 5 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
Repo: dpdk-next-virtio
38838:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 succeeded at 270 with fuzz 1 (offset -8 lines).
Hunk #2 succeeded at 374 with fuzz 1 (offset -12 lines).
Hunk #3 succeeded at 702 (offset -11 lines).
Hunk #4 FAILED at 1042.
Hunk #5 FAILED at 1123.
2 out of 5 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
Repo: dpdk-next-eventdev
38838:
patching file drivers/net/tap/rte_eth_tap.c
Hunk #1 succeeded at 270 with fuzz 1 (offset -8 lines).
Hunk #2 succeeded at 374 with fuzz 1 (offset -12 lines).
Hunk #3 succeeded at 702 (offset -11 lines).
Hunk #4 FAILED at 1042.
Hunk #5 FAILED at 1123.
2 out of 5 hunks FAILED -- saving rejects to file drivers/net/tap/rte_eth_tap.c.rej
DPDK STV team
reply other threads:[~2018-05-07 15:08 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$1jbmep@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=ferruh.yigit@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).