* [dpdk-test-report] |FAILURE| pw38291 [PATCH v11 04/10] crypto/virtio: support session related ops
@ 2018-04-28 10:37 sys_stv
0 siblings, 0 replies; only message in thread
From: sys_stv @ 2018-04-28 10:37 UTC (permalink / raw)
To: test-report; +Cc: jianjay.zhou
[-- Attachment #1: Type: text/plain, Size: 2736 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38291
_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
38291:
The next patch would create the file drivers/crypto/virtio/virtio_crypto_algs.h,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/crypto/virtio/virtio_cryptodev.c
Hunk #1 FAILED at 1.
Hunk #2 succeeded at 65 (offset 34 lines).
Hunk #3 succeeded at 294 with fuzz 2 (offset 243 lines).
Hunk #4 FAILED at 505.
Hunk #5 succeeded at 1803 (offset 997 lines).
2 out of 5 hunks FAILED -- saving rejects to file drivers/crypto/virtio/virtio_cryptodev.c.rej
patching file drivers/crypto/virtio/virtio_cryptodev.h
Hunk #1 succeeded at 25 with fuzz 2 (offset 8 lines).
Repo: dpdk-next-crypto
38291:
The next patch would create the file drivers/crypto/virtio/virtio_crypto_algs.h,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/crypto/virtio/virtio_cryptodev.c
Hunk #1 FAILED at 1.
Hunk #2 succeeded at 65 (offset 34 lines).
Hunk #3 succeeded at 294 with fuzz 2 (offset 243 lines).
Hunk #4 FAILED at 505.
Hunk #5 succeeded at 1803 (offset 997 lines).
2 out of 5 hunks FAILED -- saving rejects to file drivers/crypto/virtio/virtio_cryptodev.c.rej
patching file drivers/crypto/virtio/virtio_cryptodev.h
Hunk #1 succeeded at 25 with fuzz 2 (offset 8 lines).
Repo: dpdk-next-net
38291:
The next patch would create the file drivers/crypto/virtio/virtio_crypto_algs.h,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/crypto/virtio/virtio_cryptodev.c
Hunk #1 FAILED at 1.
Hunk #2 succeeded at 65 (offset 34 lines).
Hunk #3 succeeded at 294 with fuzz 2 (offset 243 lines).
Hunk #4 FAILED at 505.
Hunk #5 succeeded at 1803 (offset 997 lines).
2 out of 5 hunks FAILED -- saving rejects to file drivers/crypto/virtio/virtio_cryptodev.c.rej
patching file drivers/crypto/virtio/virtio_cryptodev.h
Hunk #1 succeeded at 25 with fuzz 2 (offset 8 lines).
DPDK STV team
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-04-28 10:37 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-04-28 10:37 [dpdk-test-report] |FAILURE| pw38291 [PATCH v11 04/10] crypto/virtio: support session related ops sys_stv
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).