From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: shijith.thotton@caviumnetworks.com
Subject: [dpdk-test-report] |FAILURE| pw22378 [PATCH v3 06/46] net/liquidio: liquidio device init
Date: 27 Mar 2017 10:12:00 -0700 [thread overview]
Message-ID: <ffb989$1uht1e@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1767 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/22378
_apply patch file failure_
Submitter: Shijith Thotton <shijith.thotton@caviumnetworks.com>
Date: Sat, 25 Mar 2017 11:54:54 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:78e5f2a8a133e885d5d0b5e49547b1cbcf3797fa
Repo:dpdk-next-crypto, Branch:master, CommitID:4b3ab12a495474aea01ebddc8cb23e8bc9b6d58b
Repo:dpdk-next-net, Branch:master, CommitID:147b2df7a0c6ad560261fd6b5f8e1400fb9f2221
Repo:dpdk-next-virtio, Branch:master, CommitID:922c87ff9fc456921ee5b673ac747da420f63bae
Repo:dpdk, Branch:master, CommitID:5b2976c718e0717f5e1b39b50ac71fb2ce80e47c
Apply patch file failed:
Repo: dpdk-next-net
22378:
patching file drivers/net/liquidio/Makefile
Hunk #1 FAILED at 51.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/liquidio/Makefile.rej
The next patch would create the file drivers/net/liquidio/base/lio_23xx_vf.c,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/net/liquidio/base/lio_23xx_vf.h,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/liquidio/base/lio_hw_defs.h
Hunk #1 succeeded at 93 with fuzz 2 (offset 51 lines).
patching file drivers/net/liquidio/lio_ethdev.c
Hunk #1 FAILED at 37.
Hunk #2 FAILED at 84.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/liquidio/lio_ethdev.c.rej
patching file drivers/net/liquidio/lio_struct.h
Hunk #1 FAILED at 43.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/liquidio/lio_struct.h.rej
DPDK STV team
reply other threads:[~2017-03-27 17:12 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$1uht1e@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=shijith.thotton@caviumnetworks.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).