From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: ych@panath.cn
Subject: [dpdk-test-report] |FAILURE| pw40240 [PATCH 2/2] fix Coding Style
Date: 20 May 2018 19:07:15 -0700 [thread overview]
Message-ID: <0590c7$1msphp@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1704 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/40240
_apply patch file failure_
Submitter: chuhong yao <ych@panath.cn>
Date: Mon, 21 May 2018 09:15:07 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:3c955492b601d65402c02ac81dfdc7eeb62f23c9
Repo:dpdk-next-crypto, Branch:master, CommitID:017353a4d9fe10e39b10d433418161791f6e34a2
Repo:dpdk-next-net, Branch:master, CommitID:6ab41e2f19bcd4dd7f02176ee86a4e2c42f3da61
Repo:dpdk-next-virtio, Branch:master, CommitID:317fe244a65ea2a5753e839f7d094b3d8677fac6
Repo:dpdk, Branch:master, CommitID:999951c86bcb95b3c72a193a15f01692045544fc
Apply patch file failed:
Repo: dpdk
40240:
patching file drivers/net/liquidio/lio_ethdev.c
Hunk #1 FAILED at 1405.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/liquidio/lio_ethdev.c.rej
Repo: dpdk-next-crypto
40240:
patching file drivers/net/liquidio/lio_ethdev.c
Hunk #1 FAILED at 1405.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/liquidio/lio_ethdev.c.rej
Repo: dpdk-next-net
40240:
patching file drivers/net/liquidio/lio_ethdev.c
Hunk #1 FAILED at 1405.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/liquidio/lio_ethdev.c.rej
Repo: dpdk-next-virtio
40240:
patching file drivers/net/liquidio/lio_ethdev.c
Hunk #1 FAILED at 1405.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/liquidio/lio_ethdev.c.rej
Repo: dpdk-next-eventdev
40240:
patching file drivers/net/liquidio/lio_ethdev.c
Hunk #1 FAILED at 1405.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/liquidio/lio_ethdev.c.rej
DPDK STV team
reply other threads:[~2018-05-21 2:07 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$1msphp@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=ych@panath.cn \
/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).