automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: hemant.agrawal@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw22309 [PATCH v10 11/22] net/dpaa2: add support for promiscuous mode
Date: 26 Mar 2017 12:24:54 -0700	[thread overview]
Message-ID: <e81775$11j3jjh@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Fri, 24 Mar 2017 19:05:21 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:78e5f2a8a133e885d5d0b5e49547b1cbcf3797fa
                   Repo:dpdk-next-crypto, Branch:master, CommitID:1b16ada4eeeb8c021c6b91692d0b80ecb3d9702e
                   Repo:dpdk-next-net, Branch:master, CommitID:5cb145cbca4970246064762d7c5018792411e737
                   Repo:dpdk-next-virtio, Branch:master, CommitID:922c87ff9fc456921ee5b673ac747da420f63bae
                   Repo:dpdk, Branch:master, CommitID:84aac97b49994be6b461b46be160b47938e697b3
                   
Apply patch file failed:
Repo: dpdk-next-net
22309:
patching file doc/guides/nics/features/dpaa2.ini
Hunk #1 FAILED at 5.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/nics/features/dpaa2.ini.rej
patching file drivers/net/dpaa2/dpaa2_ethdev.c
Hunk #1 FAILED at 437.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/dpaa2/dpaa2_ethdev.c.rej


DPDK STV team

             reply	other threads:[~2017-03-26 19:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-26 19:24 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-27  0:25 sys_stv
2017-03-26 22:48 sys_stv
2017-03-26 21:36 sys_stv
2017-03-26 20:32 sys_stv
2017-03-26 18:06 sys_stv
2017-03-26 16:46 sys_stv
2017-03-26 15:11 sys_stv
2017-03-26 13:41 sys_stv
2017-03-26 12:39 sys_stv
2017-03-26 11:21 sys_stv
2017-03-26 10:12 sys_stv
2017-03-26  9:10 sys_stv
2017-03-26  8:14 sys_stv
2017-03-26  7:03 sys_stv
2017-03-26  5:34 sys_stv
2017-03-26  4:05 sys_stv
2017-03-26  2:53 sys_stv
2017-03-26  1:20 sys_stv
2017-03-26  0:11 sys_stv
2017-03-25 22:46 sys_stv
2017-03-25 21:38 sys_stv
2017-03-25 20:24 sys_stv
2017-03-25 19:22 sys_stv
2017-03-25 17:40 sys_stv
2017-03-25 15:54 sys_stv
2017-03-25 14:19 sys_stv
2017-03-25 13:17 sys_stv
2017-03-25 12:10 sys_stv
2017-03-25 11:13 sys_stv

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='e81775$11j3jjh@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=hemant.agrawal@nxp.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).