From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: pbhagavatula@caviumnetworks.com
Subject: [dpdk-test-report] |FAILURE| pw37745 [PATCH v4 06/11] event/octeontx: add multiproducer timer arm and cancel
Date: 22 Apr 2018 20:03:56 -0700 [thread overview]
Message-ID: <0590c7$1fkfml@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 7191 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/37745
_apply patch file failure_
Submitter: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Date: Tue, 10 Apr 2018 02:30:32 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fe5abd3150bc1caa8369e743c395c39f53265597
Repo:dpdk-next-crypto, Branch:master, CommitID:1b71561739a8d8071b212d05040f58bba9a565d3
Repo:dpdk-next-net, Branch:master, CommitID:e5c04b1d1bc83115a2cc28615a5d5c6645c66cd4
Repo:dpdk-next-virtio, Branch:master, CommitID:ba3fec3f710a7f0289a14153500a373c4b91671d
Repo:dpdk, Branch:master, CommitID:e1d26e429a5cb0153767a5d73a0e2440b9eed2b1
Apply patch file failed:
Repo: dpdk
37745:
patching file drivers/event/octeontx/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/event/octeontx/Makefile.rej
patching file drivers/event/octeontx/meson.build
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/event/octeontx/meson.build.rej
patching file drivers/event/octeontx/timvf_evdev.c
Hunk #1 FAILED at 130.
Hunk #2 FAILED at 312.
2 out of 2 hunks FAILED -- saving rejects to file drivers/event/octeontx/timvf_evdev.c.rej
patching file drivers/event/octeontx/timvf_evdev.h
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file drivers/event/octeontx/timvf_evdev.h.rej
The next patch would create the file drivers/event/octeontx/timvf_worker.c,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/event/octeontx/timvf_worker.h,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk-next-crypto
37745:
patching file drivers/event/octeontx/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/event/octeontx/Makefile.rej
patching file drivers/event/octeontx/meson.build
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/event/octeontx/meson.build.rej
patching file drivers/event/octeontx/timvf_evdev.c
Hunk #1 FAILED at 130.
Hunk #2 FAILED at 312.
2 out of 2 hunks FAILED -- saving rejects to file drivers/event/octeontx/timvf_evdev.c.rej
patching file drivers/event/octeontx/timvf_evdev.h
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file drivers/event/octeontx/timvf_evdev.h.rej
The next patch would create the file drivers/event/octeontx/timvf_worker.c,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/event/octeontx/timvf_worker.h,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk-next-net
37745:
patching file drivers/event/octeontx/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/event/octeontx/Makefile.rej
patching file drivers/event/octeontx/meson.build
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/event/octeontx/meson.build.rej
patching file drivers/event/octeontx/timvf_evdev.c
Hunk #1 FAILED at 130.
Hunk #2 FAILED at 312.
2 out of 2 hunks FAILED -- saving rejects to file drivers/event/octeontx/timvf_evdev.c.rej
patching file drivers/event/octeontx/timvf_evdev.h
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file drivers/event/octeontx/timvf_evdev.h.rej
The next patch would create the file drivers/event/octeontx/timvf_worker.c,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/event/octeontx/timvf_worker.h,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk-next-virtio
37745:
patching file drivers/event/octeontx/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/event/octeontx/Makefile.rej
patching file drivers/event/octeontx/meson.build
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/event/octeontx/meson.build.rej
patching file drivers/event/octeontx/timvf_evdev.c
Hunk #1 FAILED at 130.
Hunk #2 FAILED at 312.
2 out of 2 hunks FAILED -- saving rejects to file drivers/event/octeontx/timvf_evdev.c.rej
patching file drivers/event/octeontx/timvf_evdev.h
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file drivers/event/octeontx/timvf_evdev.h.rej
The next patch would create the file drivers/event/octeontx/timvf_worker.c,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/event/octeontx/timvf_worker.h,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk-next-eventdev
37745:
patching file drivers/event/octeontx/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/event/octeontx/Makefile.rej
patching file drivers/event/octeontx/meson.build
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/event/octeontx/meson.build.rej
patching file drivers/event/octeontx/timvf_evdev.c
Hunk #1 FAILED at 130.
Hunk #2 FAILED at 312.
2 out of 2 hunks FAILED -- saving rejects to file drivers/event/octeontx/timvf_evdev.c.rej
patching file drivers/event/octeontx/timvf_evdev.h
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file drivers/event/octeontx/timvf_evdev.h.rej
The next patch would create the file drivers/event/octeontx/timvf_worker.c,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/event/octeontx/timvf_worker.h,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
DPDK STV team
reply other threads:[~2018-04-23 3:03 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$1fkfml@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=pbhagavatula@caviumnetworks.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).