From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: ml@napatech.com
Subject: [dpdk-test-report] |FAILURE| pw24327 [PATCH v3] net/i40e: Improved FDIR programming times
Date: 18 May 2017 02:07:33 -0700 [thread overview]
Message-ID: <ffb989$2kebq9@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1658 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/24327
_apply patch file failure_
Submitter: Michael Lilja <ml@napatech.com>
Date: Wed, 17 May 2017 00:01:32 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:776003f4a8e7af4f98338983eb2dfe0a52e8eaf5
Repo:dpdk-next-crypto, Branch:master, CommitID:3047c857a7edae2a2685c8cd72f15dee9d3c2b22
Repo:dpdk-next-net, Branch:master, CommitID:a60e71cb8fdc63ab26900b701cf728be15588f5d
Repo:dpdk-next-virtio, Branch:master, CommitID:3047c857a7edae2a2685c8cd72f15dee9d3c2b22
Repo:dpdk, Branch:master, CommitID:3047c857a7edae2a2685c8cd72f15dee9d3c2b22
Apply patch file failed:
Repo: dpdk
24327:
patching file drivers/net/i40e/i40e_fdir.c
Hunk #1 FAILED at 1296.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_fdir.c.rej
Repo: dpdk-next-crypto
24327:
patching file drivers/net/i40e/i40e_fdir.c
Hunk #1 FAILED at 1296.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_fdir.c.rej
Repo: dpdk-next-net
24327:
patching file drivers/net/i40e/i40e_fdir.c
Hunk #1 FAILED at 1296.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_fdir.c.rej
Repo: dpdk-next-virtio
24327:
patching file drivers/net/i40e/i40e_fdir.c
Hunk #1 FAILED at 1296.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_fdir.c.rej
Repo: dpdk-next-eventdev
24327:
patching file drivers/net/i40e/i40e_fdir.c
Hunk #1 FAILED at 1296.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_fdir.c.rej
DPDK STV team
reply other threads:[~2017-05-18 9: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='ffb989$2kebq9@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=ml@napatech.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).