From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: stephen@networkplumber.org
Subject: [dpdk-test-report] |FAILURE| pw38384 [PATCH v3 4/4] bus/vmbus and net/netvsc: add meson build support
Date: 01 May 2018 20:04:43 -0700 [thread overview]
Message-ID: <0590c7$1i0d57@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2618 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38384
_apply patch file failure_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 17 Apr 2018 14:53:22 -0700
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fcde84b5f85b3c1a5d5564299fd49c58ca20370d
Repo:dpdk-next-crypto, Branch:master, CommitID:211992f3b7df5d6d8f1dbefc48bc37a6d5398fbc
Repo:dpdk-next-net, Branch:master, CommitID:181cbc97812aa65a44b9c8ae4a5deb0b7640858b
Repo:dpdk-next-virtio, Branch:master, CommitID:81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
Repo:dpdk, Branch:master, CommitID:af7551e2bfceef7ddeb7941b26b06a9b6d6dee5e
Apply patch file failed:
Repo: dpdk
38384:
patching file config/meson.build
Hunk #1 succeeded at 49 (offset 4 lines).
patching file drivers/bus/meson.build
patching file drivers/bus/vmbus/meson.build
patching file drivers/net/meson.build
Hunk #1 FAILED at 3.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/meson.build.rej
patching file drivers/net/netvsc/meson.build
Repo: dpdk-next-crypto
38384:
patching file config/meson.build
Hunk #1 succeeded at 49 (offset 4 lines).
patching file drivers/bus/meson.build
patching file drivers/bus/vmbus/meson.build
patching file drivers/net/meson.build
Hunk #1 FAILED at 3.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/meson.build.rej
patching file drivers/net/netvsc/meson.build
Repo: dpdk-next-net
38384:
patching file config/meson.build
Hunk #1 succeeded at 49 (offset 4 lines).
patching file drivers/bus/meson.build
patching file drivers/bus/vmbus/meson.build
patching file drivers/net/meson.build
Hunk #1 FAILED at 3.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/meson.build.rej
patching file drivers/net/netvsc/meson.build
Repo: dpdk-next-virtio
38384:
patching file config/meson.build
Hunk #1 succeeded at 49 (offset 4 lines).
patching file drivers/bus/meson.build
patching file drivers/bus/vmbus/meson.build
patching file drivers/net/meson.build
Hunk #1 FAILED at 3.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/meson.build.rej
patching file drivers/net/netvsc/meson.build
Repo: dpdk-next-eventdev
38384:
patching file config/meson.build
Hunk #1 succeeded at 49 (offset 4 lines).
patching file drivers/bus/meson.build
patching file drivers/bus/vmbus/meson.build
patching file drivers/net/meson.build
Hunk #1 FAILED at 3.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/meson.build.rej
patching file drivers/net/netvsc/meson.build
DPDK STV team
reply other threads:[~2018-05-02 3:04 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='0590c7$1i0d57@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=stephen@networkplumber.org \
--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).