From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: jianjay.zhou@huawei.com
Subject: [dpdk-test-report] |FAILURE| pw38288 [PATCH v11 02/10] crypto/virtio: support virtio device init
Date: 28 Apr 2018 04:09:02 -0700 [thread overview]
Message-ID: <ca5293$1gb70m@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 6942 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38288
_apply patch file failure_
Submitter: Jay Zhou <jianjay.zhou@huawei.com>
Date: Tue, 17 Apr 2018 17:23:19 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fe5abd3150bc1caa8369e743c395c39f53265597
Repo:dpdk-next-crypto, Branch:master, CommitID:996096e629c3b6d08eab4acf51122ff783350b39
Repo:dpdk-next-net, Branch:master, CommitID:1a7dc2252f2862d8c783d114ab97ed490de8d160
Repo:dpdk-next-virtio, Branch:master, CommitID:81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
Repo:dpdk, Branch:master, CommitID:fcde84b5f85b3c1a5d5564299fd49c58ca20370d
Apply patch file failed:
Repo: dpdk
38288:
patching file drivers/crypto/virtio/Makefile
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/crypto/virtio/Makefile.rej
patching file drivers/crypto/virtio/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/crypto/virtio/meson.build.rej
patching file drivers/crypto/virtio/virtio_cryptodev.c
Hunk #1 FAILED at 3.
Hunk #2 FAILED at 34.
2 out of 2 hunks FAILED -- saving rejects to file drivers/crypto/virtio/virtio_cryptodev.c.rej
patching file drivers/crypto/virtio/virtio_cryptodev.h
Hunk #1 FAILED at 5.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/virtio/virtio_cryptodev.h.rej
The next patch would create the file drivers/crypto/virtio/virtio_logs.h,
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/crypto/virtio/virtio_pci.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/crypto/virtio/virtio_pci.h,
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/crypto/virtio/virtio_ring.h,
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/crypto/virtio/virtio_rxtx.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/crypto/virtio/virtqueue.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/crypto/virtio/virtqueue.h,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk-next-crypto
38288:
patching file drivers/crypto/virtio/Makefile
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/crypto/virtio/Makefile.rej
patching file drivers/crypto/virtio/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/crypto/virtio/meson.build.rej
patching file drivers/crypto/virtio/virtio_cryptodev.c
Hunk #1 FAILED at 3.
Hunk #2 FAILED at 34.
2 out of 2 hunks FAILED -- saving rejects to file drivers/crypto/virtio/virtio_cryptodev.c.rej
patching file drivers/crypto/virtio/virtio_cryptodev.h
Hunk #1 FAILED at 5.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/virtio/virtio_cryptodev.h.rej
The next patch would create the file drivers/crypto/virtio/virtio_logs.h,
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/crypto/virtio/virtio_pci.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/crypto/virtio/virtio_pci.h,
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/crypto/virtio/virtio_ring.h,
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/crypto/virtio/virtio_rxtx.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/crypto/virtio/virtqueue.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/crypto/virtio/virtqueue.h,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk-next-net
38288:
patching file drivers/crypto/virtio/Makefile
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/crypto/virtio/Makefile.rej
patching file drivers/crypto/virtio/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/crypto/virtio/meson.build.rej
patching file drivers/crypto/virtio/virtio_cryptodev.c
Hunk #1 FAILED at 3.
Hunk #2 FAILED at 34.
2 out of 2 hunks FAILED -- saving rejects to file drivers/crypto/virtio/virtio_cryptodev.c.rej
patching file drivers/crypto/virtio/virtio_cryptodev.h
Hunk #1 FAILED at 5.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/virtio/virtio_cryptodev.h.rej
The next patch would create the file drivers/crypto/virtio/virtio_logs.h,
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/crypto/virtio/virtio_pci.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/crypto/virtio/virtio_pci.h,
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/crypto/virtio/virtio_ring.h,
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/crypto/virtio/virtio_rxtx.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/crypto/virtio/virtqueue.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/crypto/virtio/virtqueue.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-28 11:09 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='ca5293$1gb70m@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=jianjay.zhou@huawei.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).