From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: adrien.mazarguil@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw39052 [PATCH v2 3/3] net/mlx4: fix inner RSS support for broken kernels
Date: 09 May 2018 04:07:35 -0700 [thread overview]
Message-ID: <ca5293$1j68q5@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1680 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/39052
_apply patch file failure_
Submitter: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Date: Thu, 26 Apr 2018 18:26:16 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:db3d585ff859251586f24f2bf60ffc276da01cda
Repo:dpdk-next-crypto, Branch:master, CommitID:aa12d5b8f9e176cac766fd199eeee25606cf5874
Repo:dpdk-next-net, Branch:master, CommitID:0e000774e1e7a4608d5bad088be95bf9949fe24a
Apply patch file failed:
Repo: dpdk
39052:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 480 with fuzz 1 (offset 93 lines).
Hunk #2 FAILED at 658.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
Repo: dpdk-next-crypto
39052:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 480 with fuzz 1 (offset 93 lines).
Hunk #2 FAILED at 658.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
Repo: dpdk-next-net
39052:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 480 with fuzz 1 (offset 93 lines).
Hunk #2 FAILED at 658.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
Repo: dpdk-next-virtio
39052:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 480 with fuzz 1 (offset 93 lines).
Hunk #2 FAILED at 658.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
Repo: dpdk-next-eventdev
39052:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 480 with fuzz 1 (offset 93 lines).
Hunk #2 FAILED at 658.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
DPDK STV team
reply other threads:[~2018-05-09 11: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='ca5293$1j68q5@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=adrien.mazarguil@6wind.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).