From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xiangxia.m.yue@gmail.com
Subject: [dpdk-test-report] |FAILURE| pw33703 [PATCH v3 4/6] net/ixgbe: write disable to ITR counter.
Date: 18 Jan 2018 17:15:07 -0800 [thread overview]
Message-ID: <a797f1$mg4hs@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1707 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/33703
_apply patch file failure_
Submitter: Tonghao Zhang <xiangxia.m.yue@gmail.com>
Date: Sun, 14 Jan 2018 02:29:34 -0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:6815f1359b0ca6c96cd9c22d1af26a4b3d794a25
Repo:dpdk-next-crypto, Branch:master, CommitID:8df8c445b4bea0a2fed921dc15766f33b48753d0
Repo:dpdk-next-net, Branch:master, CommitID:26e6baded45942b94ad9154ddd67efe8608234b4
Repo:dpdk-next-virtio, Branch:master, CommitID:9158926a0f24e9b8cccfe97211fa72d52a6f6a36
Repo:dpdk, Branch:master, CommitID:1ffee690eaa10b1b50deb230755ea4ceaa373e0f
Apply patch file failed:
Repo: dpdk
33703:
patching file drivers/net/ixgbe/ixgbe_ethdev.c
Hunk #1 FAILED at 5882.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/ixgbe/ixgbe_ethdev.c.rej
Repo: dpdk-next-crypto
33703:
patching file drivers/net/ixgbe/ixgbe_ethdev.c
Hunk #1 FAILED at 5882.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/ixgbe/ixgbe_ethdev.c.rej
Repo: dpdk-next-net
33703:
patching file drivers/net/ixgbe/ixgbe_ethdev.c
Hunk #1 FAILED at 5882.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/ixgbe/ixgbe_ethdev.c.rej
Repo: dpdk-next-virtio
33703:
patching file drivers/net/ixgbe/ixgbe_ethdev.c
Hunk #1 FAILED at 5882.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/ixgbe/ixgbe_ethdev.c.rej
Repo: dpdk-next-eventdev
33703:
patching file drivers/net/ixgbe/ixgbe_ethdev.c
Hunk #1 FAILED at 5882.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/ixgbe/ixgbe_ethdev.c.rej
DPDK STV team
reply other threads:[~2018-01-19 1:15 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='a797f1$mg4hs@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=xiangxia.m.yue@gmail.com \
/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).