From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: hemant.agrawal@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw33200 [PATCH v2 10/18] net/dpaa: optimize the Tx burst
Date: 15 Jan 2018 02:24:48 -0800 [thread overview]
Message-ID: <a797f1$l6b6n@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/33200
_apply patch file failure_
Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Tue, 9 Jan 2018 18:53:04 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:18280212534a7dcb61021393afd7394eaa1ff51e
Repo:dpdk-next-crypto, Branch:master, CommitID:84bdedea8d585c6aeccd4f258c74796d80dac66c
Repo:dpdk-next-net, Branch:master, CommitID:d33a340f42d6b7b664409b572f85707a696fcebc
Repo:dpdk-next-virtio, Branch:master, CommitID:814339ba7eea13d132508af2cccec2f73568e2d0
Repo:dpdk, Branch:master, CommitID:f477a4696572201cf26534c83a42ec7dc8098fd8
Apply patch file failed:
Repo: dpdk-next-net
33200:
patching file drivers/net/dpaa/dpaa_rxtx.c
Hunk #1 succeeded at 295 with fuzz 2 (offset 23 lines).
Hunk #2 FAILED at 618.
Hunk #3 FAILED at 694.
Hunk #4 FAILED at 709.
Hunk #5 FAILED at 753.
4 out of 5 hunks FAILED -- saving rejects to file drivers/net/dpaa/dpaa_rxtx.c.rej
DPDK STV team
reply other threads:[~2018-01-15 10:24 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$l6b6n@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=hemant.agrawal@nxp.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).