automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: shreyansh.jain@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw29340 [PATCH 2/2] config: fix DPAA PMD linking
Date: 28 Sep 2017 21:05:00 -0700	[thread overview]
Message-ID: <8a7c36$132c2he@orsmga001.jf.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Shreyansh Jain <shreyansh.jain@nxp.com>
Date: Thu, 28 Sep 2017 19:40:45 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:b4b3260b63d2d8d76ff1c66ab4b70e6d1b6a4bbe
                   Repo:dpdk-next-crypto, Branch:master, CommitID:a5a8c6976dc4ee5d5b214ec275c2735f9318fdbe
                   Repo:dpdk-next-net, Branch:master, CommitID:b4fd9dcfcec56db1caa127cd03362500f9d5bd6b
                   Repo:dpdk-next-virtio, Branch:master, CommitID:fee08fe0d67d46639d25c201738d9b1b867e443c
                   Repo:dpdk, Branch:master, CommitID:5dce9fcdb2308becb7de7470118af3eeccfe4fd7
                   
Apply patch file failed:
Repo: dpdk
29340:
patching file mk/rte.app.mk
Hunk #1 FAILED at 117.
1 out of 1 hunk FAILED -- saving rejects to file mk/rte.app.mk.rej

Repo: dpdk-next-crypto
29340:
patching file mk/rte.app.mk
Hunk #1 FAILED at 117.
1 out of 1 hunk FAILED -- saving rejects to file mk/rte.app.mk.rej

Repo: dpdk-next-net
29340:
patching file mk/rte.app.mk
Hunk #1 FAILED at 117.
1 out of 1 hunk FAILED -- saving rejects to file mk/rte.app.mk.rej

Repo: dpdk-next-virtio
29340:
patching file mk/rte.app.mk
Hunk #1 FAILED at 117.
1 out of 1 hunk FAILED -- saving rejects to file mk/rte.app.mk.rej

Repo: dpdk-next-eventdev
29340:
patching file mk/rte.app.mk
Hunk #1 FAILED at 117.
1 out of 1 hunk FAILED -- saving rejects to file mk/rte.app.mk.rej


DPDK STV team

                 reply	other threads:[~2017-09-29  4:05 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='8a7c36$132c2he@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=shreyansh.jain@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).