automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report]  |FAILURE| pw56132[v7, 2/4] net/mlx5: support match GRE protocol on DR engine
Date: 09 Jul 2019 20:55:03 -0700	[thread overview]
Message-ID: <ee68f5$7dp9v9@orsmga001.jf.intel.com> (raw)

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

Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/56132

_apply issues_

Submitter: Xiaoyu Min <jackmin@mellanox.com>
Date: 2019-07-05 09:54:24
Reply_mail: a923bb70c695b3545b0e5ba905ae58561b3bcdac.1562320050.git.jackmin@mellanox.com
DPDK git baseline:
	Repo:dpdk-next-net, CommitID: db25a1e5e9685303966b346fe3f83374b777db75
	Repo:dpdk, CommitID: cc091931dc05212db32ddbd7da3031104ca4963f

Apply patchset failed, the failed patch is:                                    http://dpdk.org/patch/56131

DPDK STV team

                 reply	other threads:[~2019-07-10  3:55 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='ee68f5$7dp9v9@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.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).