[dpdk-test-report] |FAILURE| pw38103 [PATCH v8 01/11] crypto/virtio: add virtio crypto PMD

sys_stv at intel.com sys_stv at intel.com
Thu Apr 26 17:03:31 CEST 2018


Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38103

_apply patch file failure_

Submitter: Jay Zhou <jianjay.zhou at huawei.com>
Date: Sat, 14 Apr 2018 17:34:32 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fe5abd3150bc1caa8369e743c395c39f53265597
                   Repo:dpdk-next-crypto, Branch:master, CommitID:eb8a86e275ef15a5455948d679d1a2c43dd4c740
                   Repo:dpdk-next-net, Branch:master, CommitID:0f20d3a0d4f4b6ade16edd689901795e1c4ac5cb
Apply patch file failed:
Repo: dpdk
38103:
patching file MAINTAINERS
Hunk #1 succeeded at 776 with fuzz 2 (offset 18 lines).
patching file config/common_base
Hunk #1 succeeded at 505 with fuzz 1 (offset 12 lines).
patching file doc/guides/rel_notes/release_18_05.rst
Hunk #1 succeeded at 140 with fuzz 2 (offset 58 lines).
patching file drivers/crypto/Makefile
Hunk #1 FAILED at 21.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/Makefile.rej
The next patch would create the file drivers/crypto/virtio/Makefile,
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/rte_pmd_virtio_crypto_version.map,
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_cryptodev.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_cryptodev.h,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
patching file mk/rte.app.mk
Hunk #1 succeeded at 210 (offset 2 lines).

Repo: dpdk-next-crypto
38103:
patching file MAINTAINERS
Hunk #1 succeeded at 777 with fuzz 2 (offset 19 lines).
patching file config/common_base
Hunk #1 succeeded at 505 with fuzz 1 (offset 12 lines).
patching file doc/guides/rel_notes/release_18_05.rst
Hunk #1 succeeded at 134 (offset 52 lines).
patching file drivers/crypto/Makefile
Hunk #1 FAILED at 21.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/Makefile.rej
The next patch would create the file drivers/crypto/virtio/Makefile,
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/rte_pmd_virtio_crypto_version.map,
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_cryptodev.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_cryptodev.h,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
patching file mk/rte.app.mk
Hunk #1 succeeded at 210 (offset 2 lines).

Repo: dpdk-next-net
38103:
patching file MAINTAINERS
Hunk #1 succeeded at 782 with fuzz 2 (offset 24 lines).
patching file config/common_base
Hunk #1 succeeded at 506 with fuzz 1 (offset 13 lines).
patching file doc/guides/rel_notes/release_18_05.rst
Hunk #1 succeeded at 16 with fuzz 2 (offset -66 lines).
patching file drivers/crypto/Makefile
Hunk #1 FAILED at 21.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/Makefile.rej
The next patch would create the file drivers/crypto/virtio/Makefile,
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/rte_pmd_virtio_crypto_version.map,
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_cryptodev.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_cryptodev.h,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
patching file mk/rte.app.mk
Hunk #1 succeeded at 213 (offset 5 lines).

Repo: dpdk-next-virtio
38103:
patching file MAINTAINERS
Hunk #1 succeeded at 766 (offset 8 lines).
patching file config/common_base
Hunk #1 succeeded at 494 (offset 1 line).
patching file doc/guides/rel_notes/release_18_05.rst
Hunk #1 succeeded at 115 (offset 33 lines).
patching file drivers/crypto/Makefile
Hunk #1 FAILED at 21.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/Makefile.rej
patching file drivers/crypto/virtio/Makefile
patching file drivers/crypto/virtio/rte_pmd_virtio_crypto_version.map
patching file drivers/crypto/virtio/virtio_cryptodev.c
patching file drivers/crypto/virtio/virtio_cryptodev.h
patching file mk/rte.app.mk
Hunk #1 succeeded at 209 (offset 1 line).

Repo: dpdk-next-eventdev
38103:
patching file MAINTAINERS
Hunk #1 succeeded at 759 (offset 1 line).
patching file config/common_base
patching file doc/guides/rel_notes/release_18_05.rst
Hunk #1 succeeded at 77 with fuzz 2 (offset -5 lines).
patching file drivers/crypto/Makefile
Hunk #1 FAILED at 21.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/Makefile.rej
patching file drivers/crypto/virtio/Makefile
patching file drivers/crypto/virtio/rte_pmd_virtio_crypto_version.map
patching file drivers/crypto/virtio/virtio_cryptodev.c
patching file drivers/crypto/virtio/virtio_cryptodev.h
patching file mk/rte.app.mk


DPDK STV team


More information about the test-report mailing list