From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: ferruh.yigit@intel.com
Subject: [dpdk-test-report] |FAILURE| pw31168 [PATCH v2] igb_uio: add config option to control reset
Date: 03 Nov 2017 15:21:08 -0700 [thread overview]
Message-ID: <1a8a4b$145psc5@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2275 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/31168
_apply patch file failure_
Submitter: Ferruh Yigit <ferruh.yigit@intel.com>
Date: Fri, 3 Nov 2017 15:03:34 -0700
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:b96273bb75fbd99a9732aa4d49658a3525b225b0
Repo:dpdk-next-crypto, Branch:master, CommitID:6fb00f8baefa03b9cfd1b2dfc1787258b8459601
Repo:dpdk-next-net, Branch:master, CommitID:9b0c11b32f27918d5aff7df2ff97c5be98047227
Repo:dpdk-next-virtio, Branch:master, CommitID:4f761c94b520ce71c56be1c913e54a4179b81c43
Repo:dpdk, Branch:master, CommitID:6fb00f8baefa03b9cfd1b2dfc1787258b8459601
Apply patch file failed:
Repo: dpdk
31168:
patching file lib/librte_eal/linuxapp/igb_uio/compat.h
patching file lib/librte_eal/linuxapp/igb_uio/igb_uio.c
Hunk #1 succeeded at 348 with fuzz 1.
Hunk #2 FAILED at 368.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/igb_uio/igb_uio.c.rej
Repo: dpdk-next-crypto
31168:
patching file lib/librte_eal/linuxapp/igb_uio/compat.h
patching file lib/librte_eal/linuxapp/igb_uio/igb_uio.c
Hunk #1 succeeded at 348 with fuzz 1.
Hunk #2 FAILED at 368.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/igb_uio/igb_uio.c.rej
Repo: dpdk-next-net
31168:
patching file lib/librte_eal/linuxapp/igb_uio/compat.h
patching file lib/librte_eal/linuxapp/igb_uio/igb_uio.c
Hunk #1 succeeded at 348 with fuzz 1.
Hunk #2 FAILED at 368.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/igb_uio/igb_uio.c.rej
Repo: dpdk-next-virtio
31168:
patching file lib/librte_eal/linuxapp/igb_uio/compat.h
patching file lib/librte_eal/linuxapp/igb_uio/igb_uio.c
Hunk #1 succeeded at 350 with fuzz 1 (offset 2 lines).
Hunk #2 FAILED at 368.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/igb_uio/igb_uio.c.rej
Repo: dpdk-next-eventdev
31168:
patching file lib/librte_eal/linuxapp/igb_uio/compat.h
patching file lib/librte_eal/linuxapp/igb_uio/igb_uio.c
Hunk #1 succeeded at 348 with fuzz 1.
Hunk #2 FAILED at 368.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/igb_uio/igb_uio.c.rej
DPDK STV team
reply other threads:[~2017-11-03 22:21 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='1a8a4b$145psc5@fmsmga001.fm.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).