From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: shahafs@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw39929 [PATCH 2/3] ethdev: fail if Tx queue offload is not supported at all Re: [PATCH] [PATCH 2/3] ethdev: fail if Tx queue offload is not> supported at all> > -----Original Message-----> >
Date: 14 May 2018 23:40:27 -0700 [thread overview]
Message-ID: <ca5293$1kmra9@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/39929
_apply patch file failure_
Submitter: Shahaf Shuler <shahafs@mellanox.com>
Date: Sun, 13 May 2018 13:30:25 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:3c955492b601d65402c02ac81dfdc7eeb62f23c9
Repo:dpdk-next-crypto, Branch:master, CommitID:e0d88a394e91f446234aa04d0f9e01c150b0d347
Repo:dpdk-next-net, Branch:master, CommitID:5b18d86decf86ba4789a2c2de7b2624f2e9fa1b0
Repo:dpdk-next-virtio, Branch:master, CommitID:037c0996bc927342f157426739e0cb63f2db8689
Repo:dpdk, Branch:master, CommitID:ff75dd7d651e71213074a18e4a93e1ba612e84f7
Apply patch file failed:
Repo: dpdk
39929:
patching file lib/librte_ethdev/rte_ethdev.c
Hunk #1 FAILED at 1727.
Repo: dpdk-next-crypto
39929:
patching file lib/librte_ethdev/rte_ethdev.c
Hunk #1 FAILED at 1727.
Repo: dpdk-next-net
39929:
patching file lib/librte_ethdev/rte_ethdev.c
Hunk #1 FAILED at 1727.
Repo: dpdk-next-virtio
39929:
patching file lib/librte_ethdev/rte_ethdev.c
Hunk #1 FAILED at 1727.
Repo: dpdk-next-eventdev
39929:
patching file lib/librte_ethdev/rte_ethdev.c
Hunk #1 FAILED at 1727.
DPDK STV team
reply other threads:[~2018-05-15 6:40 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='ca5293$1kmra9@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=shahafs@mellanox.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).