From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: hemant.agrawal@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw27973 [PATCH 18/27] bus/fslmc: enable link status interrupt
Date: 25 Aug 2017 07:48:38 -0700 [thread overview]
Message-ID: <7327ef$3q8j8h@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/27973
_apply patch file failure_
Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Fri, 25 Aug 2017 16:19:31 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:85238f501ec36bc6f0e15e6434296312841259bd
Repo:dpdk-next-crypto, Branch:master, CommitID:85238f501ec36bc6f0e15e6434296312841259bd
Repo:dpdk-next-net, Branch:master, CommitID:729fab783ca0b6a44281112285d58250b459ba09
Repo:dpdk-next-virtio, Branch:master, CommitID:6c157fe64650167646ff1312f9f7e7dc3674d7eb
Repo:dpdk, Branch:master, CommitID:85238f501ec36bc6f0e15e6434296312841259bd
Apply patch file failed:
Repo: dpdk
27973:
patching file drivers/bus/fslmc/fslmc_vfio.c
Hunk #1 FAILED at 464.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/fslmc/fslmc_vfio.c.rej
Repo: dpdk-next-crypto
27973:
patching file drivers/bus/fslmc/fslmc_vfio.c
Hunk #1 FAILED at 464.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/fslmc/fslmc_vfio.c.rej
Repo: dpdk-next-net
27973:
patching file drivers/bus/fslmc/fslmc_vfio.c
Hunk #1 FAILED at 464.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/fslmc/fslmc_vfio.c.rej
Repo: dpdk-next-virtio
27973:
patching file drivers/bus/fslmc/fslmc_vfio.c
Hunk #1 FAILED at 464.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/fslmc/fslmc_vfio.c.rej
Repo: dpdk-next-eventdev
27973:
patching file drivers/bus/fslmc/fslmc_vfio.c
Hunk #1 FAILED at 464.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/fslmc/fslmc_vfio.c.rej
DPDK STV team
reply other threads:[~2017-08-25 14:48 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='7327ef$3q8j8h@orsmga002.jf.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).