From: sys_stv@intel.com
To: yongjiex.gu@intel.com, weichunx.chen@intel.com,
huilongx.xu@intel.com, gangx.xu@intel.com, peipeix.lu@intel.com,
nelio.laranjeiro@6wind.com, test-report@dpdk.org
Subject: [dpdk-test-report] [Patchwork]|ERROR| pw16798 net/mlx5: fix support for newer link speeds
Date: 26 Oct 2016 03:01:01 -0700 [thread overview]
Message-ID: <85fdc9$1023bij@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 16798
http://www.dpdk.org/dev/patchwork/patch/16798/
Submitter: =?utf-8?q?N=C3=A9lio_Laranjeiro?= <nelio.laranjeiro@6wind.com>
Date: Wed, 26 Oct 2016 11:44:02 +0200
DPDK git baseline: dbffbf80e99aad7c7a5ffaf78e750ae69963f9e0
Check patch:Success
patch file error:
16798:
patching file drivers/net/mlx5/Makefile
patching file drivers/net/mlx5/mlx5_ethdev.c
Hunk #1 FAILED at 627.
Hunk #2 succeeded at 682 (offset -9 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_ethdev.c.rej
DPDK STV team
reply other threads:[~2016-10-26 10:01 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='85fdc9$1023bij@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=gangx.xu@intel.com \
--cc=huilongx.xu@intel.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=peipeix.lu@intel.com \
--cc=test-report@dpdk.org \
--cc=weichunx.chen@intel.com \
--cc=yongjiex.gu@intel.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).