From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: bernard.iremonger@intel.com
Subject: [dpdk-test-report] |FAILURE| pw22187 [PATCH v2 1/3] net/i40e: add QinQ wrapper function
Date: 23 Mar 2017 22:38:10 -0700 [thread overview]
Message-ID: <e81775$11ia4mv@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3348 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/22187
_apply patch file failure_
Submitter: Bernard Iremonger <bernard.iremonger@intel.com>
Date: Thu, 23 Mar 2017 16:38:31 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:1df5f2222142242be872e47628a22e0bd0887a81
Repo:dpdk-next-crypto, Branch:master, CommitID:1b16ada4eeeb8c021c6b91692d0b80ecb3d9702e
Repo:dpdk-next-net, Branch:master, CommitID:b36be54c55e82610c801d1db842ee229e389a7ce
Repo:dpdk-next-virtio, Branch:master, CommitID:922c87ff9fc456921ee5b673ac747da420f63bae
Repo:dpdk, Branch:master, CommitID:84aac97b49994be6b461b46be160b47938e697b3
Apply patch file failed:
Repo: dpdk
22187:
patching file drivers/net/i40e/i40e_ethdev.c
Hunk #2 succeeded at 6666 (offset -21 lines).
Hunk #3 succeeded at 7043 with fuzz 2 (offset 10 lines).
Hunk #4 FAILED at 7065.
Hunk #5 succeeded at 11235 with fuzz 2 (offset -490 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.c.rej
patching file drivers/net/i40e/i40e_ethdev.h
Hunk #1 FAILED at 504.
Hunk #2 FAILED at 552.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.h.rej
Repo: dpdk-next-crypto
22187:
patching file drivers/net/i40e/i40e_ethdev.c
Hunk #2 succeeded at 6666 (offset -21 lines).
Hunk #3 succeeded at 7043 with fuzz 2 (offset 10 lines).
Hunk #4 FAILED at 7065.
Hunk #5 succeeded at 11235 with fuzz 2 (offset -490 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.c.rej
patching file drivers/net/i40e/i40e_ethdev.h
Hunk #1 FAILED at 504.
Hunk #2 FAILED at 552.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.h.rej
Repo: dpdk-next-net
22187:
patching file drivers/net/i40e/i40e_ethdev.c
Hunk #3 succeeded at 7064 with fuzz 2 (offset 31 lines).
Hunk #4 FAILED at 7065.
Hunk #5 succeeded at 11282 with fuzz 2 (offset -443 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.c.rej
patching file drivers/net/i40e/i40e_ethdev.h
Hunk #1 FAILED at 504.
Hunk #2 FAILED at 552.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.h.rej
Repo: dpdk-next-virtio
22187:
patching file drivers/net/i40e/i40e_ethdev.c
Hunk #2 succeeded at 6666 (offset -21 lines).
Hunk #3 succeeded at 7043 with fuzz 2 (offset 10 lines).
Hunk #4 FAILED at 7065.
Hunk #5 succeeded at 11235 with fuzz 2 (offset -490 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.c.rej
patching file drivers/net/i40e/i40e_ethdev.h
Hunk #1 FAILED at 504.
Hunk #2 FAILED at 552.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.h.rej
Repo: dpdk-next-eventdev
22187:
patching file drivers/net/i40e/i40e_ethdev.c
Hunk #2 succeeded at 6666 (offset -21 lines).
Hunk #3 succeeded at 7043 with fuzz 2 (offset 10 lines).
Hunk #4 FAILED at 7065.
Hunk #5 succeeded at 11235 with fuzz 2 (offset -490 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.c.rej
patching file drivers/net/i40e/i40e_ethdev.h
Hunk #1 FAILED at 504.
Hunk #2 FAILED at 552.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/i40e/i40e_ethdev.h.rej
DPDK STV team
reply other threads:[~2017-03-24 5:38 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$11ia4mv@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=bernard.iremonger@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).