automatic DPDK test reports
 help / color / mirror / Atom feed
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| pw16894 net/mlx5: define explicit fields for Rx offloads
Date: 02 Nov 2016 04:33:24 -0700	[thread overview]
Message-ID: <532f2c$vli9sg@fmsmga001.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]

Test-Label: Intel Niantic on Fedora
Test-Status: ERROR

Patchwork ID: 16894
http://www.dpdk.org/dev/patchwork/patch/16894/
Submitter: =?utf-8?q?N=C3=A9lio_Laranjeiro?= <nelio.laranjeiro@6wind.com>
Date: Wed,  2 Nov 2016 11:39:38 +0100
DPDK git baseline: ca41215c051a1f4f6f96e947ccb671dab3509cbf

Check patch:Success

patch file error:
16894: 
patching file drivers/net/mlx5/mlx5_prm.h
Hunk #1 succeeded at 137 (offset -21 lines).
patching file drivers/net/mlx5/mlx5_rxtx.c
Hunk #1 succeeded at 81 (offset -2 lines).
Hunk #2 succeeded at 99 (offset -2 lines).
Hunk #3 succeeded at 117 (offset -2 lines).
Hunk #4 succeeded at 136 (offset -2 lines).
Hunk #5 succeeded at 172 (offset -2 lines).
Hunk #6 FAILED at 1090.
Hunk #7 succeeded at 1136 (offset -2 lines).
Hunk #8 succeeded at 1147 (offset -2 lines).
Hunk #9 succeeded at 1165 (offset -2 lines).
Hunk #10 succeeded at 1177 (offset -2 lines).
Hunk #11 succeeded at 1186 (offset -2 lines).
Hunk #12 succeeded at 1230 (offset -2 lines).
Hunk #13 FAILED at 1255.
Hunk #14 succeeded at 1286 (offset -2 lines).
Hunk #15 succeeded at 1324 (offset -2 lines).
2 out of 15 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.c.rej

DPDK STV team 

                 reply	other threads:[~2016-11-02 11:33 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='532f2c$vli9sg@fmsmga001.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).