From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: wei.zhao1@intel.com
Subject: [dpdk-test-report] |FAILURE| pw25254 [PATCH v4 11/11] net/e1000: flush all the filter
Date: 12 Jun 2017 17:41:11 -0700 [thread overview]
Message-ID: <ffb989$2u3i3u@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1752 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/25254
_apply patch file failure_
Submitter: zhao wei <wei.zhao1@intel.com>
Date: Mon, 12 Jun 2017 14:30:06 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:a93a816c27484017b86af9d19566218a846251f1
Repo:dpdk-next-crypto, Branch:master, CommitID:b1cac453935eb8d2f1dee8e7ab081711cfb0cf70
Repo:dpdk-next-net, Branch:master, CommitID:6110b1c65ba01d2cce03b6c1640dfe519c6f5884
Repo:dpdk-next-virtio, Branch:master, CommitID:101a00a4811479e7f66829e523c9138288831b39
Repo:dpdk, Branch:master, CommitID:a6793d47f328354d0a3a3984060bbfb967e4f91d
Apply patch file failed:
Repo: dpdk-next-net
25254:
patching file drivers/net/e1000/e1000_ethdev.h
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/net/e1000/e1000_ethdev.h.rej
patching file drivers/net/e1000/igb_ethdev.c
Hunk #1 succeeded at 1061 (offset 49 lines).
Hunk #2 succeeded at 3968 (offset 115 lines).
Hunk #3 succeeded at 4779 with fuzz 1 (offset 893 lines).
Hunk #4 FAILED at 3905.
Hunk #5 FAILED at 3974.
Hunk #6 succeeded at 5016 with fuzz 2 (offset 621 lines).
Hunk #7 succeeded at 5804 with fuzz 2 (offset 1372 lines).
Hunk #8 FAILED at 4451.
Hunk #9 FAILED at 4715.
4 out of 9 hunks FAILED -- saving rejects to file drivers/net/e1000/igb_ethdev.c.rej
patching file drivers/net/e1000/igb_flow.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/net/e1000/igb_flow.c.rej
DPDK STV team
reply other threads:[~2017-06-13 0:41 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='ffb989$2u3i3u@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=wei.zhao1@intel.com \
/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).