From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: yskoh@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw32762 [PATCH 5/5] net/mlx5: clean up multi-segment packet processing
Date: 11 Jan 2018 09:34:19 -0800 [thread overview]
Message-ID: <b11803$8uns4@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1711 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/32762
_apply patch file failure_
Submitter: Yongseok Koh <yskoh@mellanox.com>
Date: Tue, 26 Dec 2017 19:55:43 -0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:18280212534a7dcb61021393afd7394eaa1ff51e
Repo:dpdk-next-crypto, Branch:master, CommitID:052f7e585e9c7c5f2bbacb230812df95e774e98e
Repo:dpdk-next-net, Branch:master, CommitID:32287ded21fdef4bfbe0151f48b9a632338e6e52
Repo:dpdk-next-virtio, Branch:master, CommitID:814339ba7eea13d132508af2cccec2f73568e2d0
Repo:dpdk, Branch:master, CommitID:f06125c07d6203a84e9b242c62d6a8e532a5c51d
Apply patch file failed:
Repo: dpdk
32762:
patching file drivers/net/mlx5/mlx5_rxtx.c
Hunk #1 FAILED at 1351.
Hunk #2 succeeded at 1402 (offset 28 lines).
Hunk #3 succeeded at 1446 (offset 28 lines).
Hunk #4 succeeded at 1555 (offset 28 lines).
1 out of 4 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.c.rej
Repo: dpdk-next-crypto
32762:
patching file drivers/net/mlx5/mlx5_rxtx.c
Hunk #1 FAILED at 1351.
Hunk #2 succeeded at 1402 (offset 28 lines).
Hunk #3 succeeded at 1446 (offset 28 lines).
Hunk #4 succeeded at 1555 (offset 28 lines).
1 out of 4 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.c.rej
Repo: dpdk-next-eventdev
32762:
patching file drivers/net/mlx5/mlx5_rxtx.c
Hunk #1 FAILED at 1351.
Hunk #2 succeeded at 1402 (offset 28 lines).
Hunk #3 succeeded at 1446 (offset 28 lines).
Hunk #4 succeeded at 1555 (offset 28 lines).
1 out of 4 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.c.rej
DPDK STV team
reply other threads:[~2018-01-11 17:34 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='b11803$8uns4@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=yskoh@mellanox.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).