From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: emmanuel.roullit@gmail.com
Subject: [dpdk-test-report] |FAILURE| pw19987 [PATCH 3/3] net/cxgbe: remove unused variable
Date: 24 Jan 2017 17:31:15 -0800 [thread overview]
Message-ID: <e81775$10njs1p@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1617 bytes --]
Test-Label: Intel compilation
Test-Status: FAILURE
http://dpdk.org/patch/19987
_apply patch file failure_
Submitter: Emmanuel Roullit <emmanuel.roullit@gmail.com>
Date: Tue, 24 Jan 2017 21:48:59 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:6297f20d662ea2494b5e7323cd0680f11968ee51
Repo:dpdk-next-crypto, Branch:master, CommitID:757c1383097291306468f152f8a0b4ce2112e055
Repo:dpdk-next-net, Branch:master, CommitID:d8cc9f7fa96df603b755c217ab44ba3067701c93
Repo:dpdk-next-virtio, Branch:master, CommitID:eeae327324d54629794ca81dffef80057c7f3b15
Repo:dpdk, Branch:master, CommitID:61207d014fc906302a184ae2f779b54ccfd0cd4c
Apply patch file failed:
Repo: dpdk
19987:
patching file drivers/net/cxgbe/sge.c
Hunk #1 FAILED at 890.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/cxgbe/sge.c.rej
Repo: dpdk-next-crypto
19987:
patching file drivers/net/cxgbe/sge.c
Hunk #1 FAILED at 890.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/cxgbe/sge.c.rej
Repo: dpdk-next-net
19987:
patching file drivers/net/cxgbe/sge.c
Hunk #1 FAILED at 890.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/cxgbe/sge.c.rej
Repo: dpdk-next-virtio
19987:
patching file drivers/net/cxgbe/sge.c
Hunk #1 FAILED at 890.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/cxgbe/sge.c.rej
Repo: dpdk-next-eventdev
19987:
patching file drivers/net/cxgbe/sge.c
Hunk #1 FAILED at 890.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/cxgbe/sge.c.rej
DPDK STV team
reply other threads:[~2017-01-25 1:31 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$10njs1p@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=emmanuel.roullit@gmail.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).